docs(js): Review and update Hapi quick start guide (#14292)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
Reviewed and updated the Hapi quick start guide

Closes: #14289 

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [x] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

Author: inventarSarah

docs/platforms/javascript/guides/hapi/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Hapi
-description: "Learn about using Sentry with Hapi."
+description: "Learn how to manually set up Sentry in your Hapi app and capture your first errors."
 sdk: sentry.javascript.node
 fallbackGuide: javascript.node
 categories:
@@ -9,8 +9,4 @@ categories:
   - server-node
 ---
 
-<PlatformContent includePath="getting-started-primer" />
-
-This guide explains how to set up Sentry in your Hapi application.
-
 <PlatformContent includePath="getting-started-node" />

platform-includes/getting-started-verify-locate-data/javascript.node.mdx

@@ -3,5 +3,6 @@
 1. Open the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues) page and select an error from the issues list to view the full details and context of this error. For an interactive UI walkthrough, click [here](/product/sentry-basics/integrate-frontend/generate-first-error/#ui-walkthrough).
 2. Open the [**Traces**](https://sentry.io/orgredirect/organizations/:orgslug/traces) page and select a trace to reveal more information about each span, its duration, and any errors. For an interactive UI walkthrough, click [here](/product/sentry-basics/distributed-tracing/generate-first-error/#ui-walkthrough).
 3. Open the [**Profiles**](https://sentry.io/orgredirect/organizations/:orgslug/profiling) page, select a transaction, and then a profile ID to view its flame graph. For more information, click [here](/product/explore/profiling/profile-details/).
+4. Open the [**Logs**](https://sentry.io/explore/logs) page and filter by service, environment, or search keywords to view log entries from your application. For an interactive UI walkthrough, click [here](/product/explore/logs/#overview).
 
 </Expandable>

platform-includes/getting-started-verify/javascript.hapi.mdx

@@ -0,0 +1,40 @@
+### Issues
+
+First, let's make sure Sentry is correctly capturing errors and creating issues in your project. Add the following code snippet to your main application file; it defines a route that will deliberately trigger an error when called:
+
+```javascript
+server.route({
+  method: "GET",
+  path: "/debug-sentry",
+  handler: (request, h) => {
+    throw new Error("My first Sentry error!");
+  },
+});
+```
+
+<OnboardingOption optionId="performance">
+
+### Tracing
+
+To test your tracing configuration, update the previous code snippet by starting a trace to measure the time it takes for the execution of your code:
+
+```javascript
+server.route({
+  method: "GET",
+  path: "/debug-sentry",
+  handler: async (request, h) => {
+    await Sentry.startSpan(
+      {
+        op: "test",
+        name: "My First Test Transaction",
+      },
+      async () => {
+        await new Promise((resolve) => setTimeout(resolve, 100));
+        throw new Error("My first Sentry error!");
+      }
+    );
+  },
+});
+```
+
+</OnboardingOption>