Belemetry can't send errors to Sentry as Issues

Abierto
  • ¿Algo no está bien?
#14,704 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@msynk ya está trabajando en esto.

Desde el 7/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
C#
Estrellas
1.4k
Forks
264
Merge medio
10 h 5 min
PR fusionados (30 d)
501

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de bitfoundation/bitplatform

Todos los issues de bitfoundation/bitplatform

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.