Connecting OpenTelemetry spans to your SDK or library's errors give the context to connect an error across teams, tools, and products to allow developers to resolve issues faster. Example such as adding spans with project IDs, URLs, or segmentation information can give developers directly actionable information or direct them to who to pull into the conversation.
| What are you looking to do? |
|---|
| Add OpenTelemetry support for errors emitted by your SDK or library |
| See example integrations |
The goal here is to connect error analysis to the full view of the distributed system by linking error events to the current tracing context.
-
Find the OpenTelemetry SDK for the language(s) or framework(s) used by your SDK
-
Import the language-specific OpenTelemetry API and patch your library method(s)
-
Use the OpenTelemetry docs to add spans, metrics, and logs to annotate errors produced by your SDK with more actionable context
- As an example, here the Rollbar SDK creates an attribute to linking back to the specific error so the developer can link to the full context of the error
- Send data from your product to an OpenTelemetry collector that outputs to the console and verify output.
- Optional: verify in an OpenTelemetry production tool of your choice
Make your code usable to as many people as possible! If you're looking for help here, contact us at partnerships@lightstep.com. We'd love to help support you!
These example solutions use plugins to generate metrics, logs or traces by automatically-instrumenting Javascript libaries or frameworks. No change to the underlying library or framework is needed.
| Instrumentation Package | Instrumented Package | What it does |
|---|---|---|
| opentelemetry-plugin-rollbar | rollbar |
emits OpenTelemetry data from the Rollbar SDK to connect Rollbar error analysis to OpenTelemetry trace data |