sentry-javascript
sentry-javascript copied to clipboard
getsentry
Official Sentry SDKs for JavaScript
### Problem Statement # Background We are running Sentry in production and have been for a while now (~2 years or so). Over the course of the last year, we...
### Is there an existing issue for this? - [X] I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues - [X] I have reviewed the documentation https://docs.sentry.io/ - [X] I am using...
### Is there an existing issue for this? - [X] I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues - [X] I have reviewed the documentation https://docs.sentry.io/ - [X] I am using...
Today, we do not support providing generator functions as a callback to `startSpan` or `startSpanManual`. This is fundamentally a bit tricky, first because it is a bit tricky (but probably...
### Problem Statement **Use case**: When an error occurs, we prompt the user for feedback and also for consent to upload diagnostic info. Diagnostic info is uploaded to cloud storage,...
Right now to implement distributed tracing with the JS SDK, it is a bit confusing. The docs jump back and forth between different concepts: https://docs.sentry.io/platforms/javascript/distributed-tracing/custom-instrumentation/ and attaching headers requires both...
### Problem Statement Our current Otel-node-specific implementation of `continueTrace` creates a remote span which holds the trace information from the `sentry-trace` and `baggage` data passed to `continueTrace` (as described in...
Followup to https://github.com/getsentry/sentry-javascript/pull/11169 In the logic where we set a span status based on `HTTP_STATUS_CODE` or `RPC_GRPC_STATUS` code, there are two inconsistencies with the spec (https://opentelemetry.io/docs/specs/semconv/rpc/grpc/): - We assume the...
```[tasklist] ### General - [ ] Update docs to add more examples around new Span APIs - [ ] Document how to override OTEL config - [ ] Update tracing...
Just a collection of things I noticed when trying out the Next.js SDK with our newest OTEL implementation. This list is WIP: Findings: - Next.js is creating spans by itself...