docs: added sentry guide (#12744)
* docs: added sentry guide * added error capturing * generate
This commit is contained in:
@@ -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)
|
||||
Reference in New Issue
Block a user