#Sentry

Has anyone tried integrating #Sentry with #Deno Deploy? Locally, error reports and traces are sent to Sentry just fine, but after deploying to Deno Deploy, nothing is sent to Sentry. Has anyone experienced this?

#DenoDeploy

Just released @logtape/sentry, a #LogTape sink for @getsentry! Now you can easily send your logs to #Sentry.

https://github.com/dahlia/logtape-sentry

#Fedify's @opentelemetry instrumentation works like a charm with @getsentry!

#OpenTelemetry #Sentry

Okay. While #Sentry SDK for #Node.js supports #OpenTelemetry integration, Sentry SDK for #Deno does not.

Does anyone have experience integrating Spans measured using the #OpenTelemetry API with #Sentry in #Node.js or #Deno?

According to the docs in the Sentry SDK, OpenTelemetry integration is out of the box and doesn't require any configuration, but Spans instrumented using the OpenTelemetry API are ignored. Spans made with the Sentry API are working fine.

https://docs.sentry.io/platforms/javascript/guides/node/opentelemetry/

I feel like I've asked this before...

I want a SaaS where I post performance results. The service would give me dashboard and monitoring/alerts.

It seems like #datadog or #sentry would be able to do something like this but I always hit limitations in what to POST and in creating the graphs.

The data I want to submit and visualize is git commit hash on the x axis and the performance number on the y axis (with optional error bar due to std dev).

Seems like an obvious thing to want? No?

Question to #Fediverse #dev friends: In recent years, many developers seem to find #Sentry necessary - a heavyweight both in terms of resource usage and data processed.
Within days, up to hundreds of GBs of data accumulate, contrasting their CMSes that are small, fast, and efficient, only a few GBs in size.

The question is: Do you think it's truly beneficial, or is it one of those things everyone does just because "everyone else does"?

#IT #SysAdmin #DevOps #Devs