docs: added sentry guide (medusajs#12744)

* docs: added sentry guide

* added error capturing

* generate

Author: shahednasser

www/apps/book/app/learn/debugging-and-testing/instrumentation/page.mdx

@@ -8,7 +8,15 @@ export const metadata = {
 
 In this chapter, you'll learn about observability in Medusa and how to configure instrumentation with OpenTelemetry.
 
-## Observability with OpenTelemtry
+## What is Instrumentation?
+
+Instrumentation is the collection of data about your application's performance and errors. It helps you debug issues, monitor performance, and gain insights into how your application behaves in production.
+
+Instrumentation and observability are crucial as you build customizations in your application. They allow you to optimize performance, identify bottlenecks, and ensure your application runs smoothly.
+
+---
+
+## Instrumentation and Observability with OpenTelemetry
 
 Medusa uses [OpenTelemetry](https://opentelemetry.io/) for instrumentation and reporting. When configured, it reports traces for:
 
@@ -158,3 +166,9 @@ Trace span names start with the following keywords based on what it's reporting:
 - `step:` when reporting a step in a workflow execution.
 - `query.graph:` when reporting Query usages.
 - `pg.query:` when reporting database queries and operations.
+
+---
+
+## Useful Links
+
+- [Integrate Sentry with Medusa](!resources!/integrations/guides/sentry)

www/apps/book/generated/edit-dates.mjs

@@ -70,7 +70,7 @@ export const generatedEditDates = {
   "app/learn/fundamentals/modules/db-operations/page.mdx": "2025-04-25T14:26:25.000Z",
   "app/learn/fundamentals/modules/multiple-services/page.mdx": "2025-03-18T15:11:44.632Z",
   "app/learn/fundamentals/modules/page.mdx": "2025-03-18T07:51:09.049Z",
-  "app/learn/debugging-and-testing/instrumentation/page.mdx": "2025-02-24T08:12:53.132Z",
+  "app/learn/debugging-and-testing/instrumentation/page.mdx": "2025-06-16T10:40:52.922Z",
   "app/learn/fundamentals/api-routes/additional-data/page.mdx": "2025-04-17T08:50:17.036Z",
   "app/learn/fundamentals/workflows/variable-manipulation/page.mdx": "2025-04-24T13:14:43.967Z",
   "app/learn/customization/custom-features/api-route/page.mdx": "2024-12-09T10:39:30.046Z",

www/apps/book/generated/sidebar.mjs

@@ -1128,7 +1128,18 @@ export const generatedSidebars = [
             "type": "link",
             "path": "/learn/debugging-and-testing/instrumentation",
             "title": "Instrumentation",
-            "children": [],
+            "children": [
+              {
+                "loaded": true,
+                "isPathHref": true,
+                "type": "ref",
+                "path": "/resources/integrations/guides/sentry",
+                "title": "Guide: Sentry",
+                "children": [],
+                "chapterTitle": "7.4.1. Guide: Sentry",
+                "number": "7.4.1."
+              }
+            ],
             "chapterTitle": "7.4. Instrumentation",
             "number": "7.4."
           },

www/apps/book/public/llms-full.txt

@@ -593,6 +593,13 @@ export const sidebars = [
             type: "link",
             path: "/learn/debugging-and-testing/instrumentation",
             title: "Instrumentation",
+            children: [
+              {
+                type: "ref",
+                path: "/resources/integrations/guides/sentry",
+                title: "Guide: Sentry",
+              },
+            ],
           },
           {
             type: "link",

www/apps/book/sidebar.mjs

@@ -692,7 +692,7 @@ export async function POST(
 }
 ```
 
-Since you export a `POST` route handler function, you expose an `API` route at `/admin/algolia/sync`. The route handler function accepts two parameters:
+Since you export a `POST` route handler function, you expose a `POST` API route at `/admin/algolia/sync`. The route handler function accepts two parameters:
 
 1. A request object with details and context on the request, such as body parameters or authenticated user details.
 2. A response object to manipulate and send the response.