Repository navigation
Built with harnsy — the Buggregator team runs its AI agents in harnsy.
Ships with Buggregator server v2.12.0. OpenTelemetry data, trace graphs and the service filter need that server.
Added
- OpenTelemetry in Sentry Traces and Logs. Traces and logs sent by OpenTelemetry SDKs or the OTel Collector appear next to Sentry ones. A trace card shows its services and where the data came from; a Source filter (Sentry / OpenTelemetry) and a Service column on both pages. (#359)
- Span details. Click a span to see its exception, Attributes, Events, Links and Resource. The root transaction is the first row of the waterfall; long stacks are folded. (#359, #360)
- Trace graphs. Next to Waterfall, a trace has Flame graph, Call graph and Sequence tabs (Sequence zooms and pans). (#361, #362)
- Service map. The traces list has List and Service map views. The map shows which services call which, with traffic over the period. Click a service to see what it uses and what uses it, or a line to see its numbers and the traces through it. (#361, #362)
- Related logs on the trace page. Every log of the trace is listed under it; a log's span link opens that span in the waterfall. (#361)
- Setup help for OpenTelemetry: OTel SDK and OTel Collector tabs on the Sentry setup help. (#359)
Fixed
- Typed Sentry log attributes show their value. (#359)
- OTel span status sits with the span, not in Attributes; a span that starts before its parent shows a real minus sign. (#360)
- Long log attribute keys wrap in their column. (#361)
Full Changelog: 1.38.0...1.39.0