Belemetry can't send errors to Sentry as Issues

Aperta
  • Qualcosa non va?
#14,704 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@msynk ci sta già lavorando.

Dal 7/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Belemetry exports to OTLP and Azure Monitor. Sentry accepts OTLP traces and logs on Relay's /otlp/v1/traces and /otlp/v1/logs routes, but nothing it receives over OTLP becomes an Issue. Span events are dropped, and exception attributes on log records stay plain strings. getsentry/sentry-dotnet#5350 was closed as by design.

So an app that wants Sentry Issues has to run a Sentry SDK next to Belemetry, and every host ends up with two pipelines for errors. The bit Boilerplate does exactly that today on the server, in WebAssembly, on Windows and on MAUI.

With an errors exporter, one pipeline could carry everything: traces, logs and metrics over OTLP, and errors as Sentry error events. What it needs:

  • Exception records become error events posted to the envelope endpoint. The DSN key is public, so the page can post as well, the way Sentry's browser SDK does.
  • .NET frames carry the method token and IL offset plus a pe_dotnet debug image, so Symbolicator adds file and line from uploaded PDBs. Neither Relay nor Sentry parses stack strings.
  • JavaScript stacks are parsed for V8, SpiderMonkey and JavaScriptCore.
  • Each event carries its trace and span ids, so an Issue links to its trace.

Native crashes on Android, iOS and Mac Catalyst are out of Belemetry's reach. They still need the Sentry SDK, run as a crash reporter only: the core Sentry package rather than Sentry.Maui, with tracing off. On those platforms the exporter would send handled errors and leave crashes to that SDK.

Lingua principale
C#
Stelle
1.4k
Fork
264
Merge medio
10h 5m
PR unite (30g)
501

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bitfoundation/bitplatform

Tutte le issue di bitfoundation/bitplatform

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.