Graph/24172262-206f-4644-aa20-e088d57324e0

Domainunvalidated

Instrumentation

24172262-206f-4644-aa20-e088d57324e0

Instrumentation

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0003

Effectiveness0.000

Connections

50 linked nodes

IMPLEMENTATION_OFComponent

quarkus

IMPLEMENTATION_OFComponent

opentelemetry

PERTAIN_TOProblem

we don't have Sentry logging anymore — since we picked Temporal to run our background tasks (workflows and activities). Tension: Is it possible to configure our worker to setup Sentry SDK and forward errors in workflows and activities to Sentry? Outcome: You can configure your worker with a Workflow interceptor.

PERTAIN_TOSolution

You can configure your worker with a Workflow interceptor — Temporal workflows and activities. Tension: we don't have Sentry logging anymore. Outcome: catch all exception raised during your activities and workflow execution.

PERTAIN_TOSolution

Set options.MinimumEventLevel = SentryLevel.Fatal for MAUI logging events, and check evt.SentryExceptions.FirstOrDefault()?.Handled to drop handled exceptions

PERTAIN_TORootCause

I have to add all these lines every time I want to measure something — According to the Sentry docs. Tension: all my different Controller methods, or places where I need to measure how long a piece of code takes. Outcome: sentry_measure_start('slow.task');.

PERTAIN_TOProblem

I'm so discouraged by how many lines of code I have to add everywhere. — According to the Sentry docs, I have to add all these lines every time I want to measure something. Tension: It would be so much duplicate code. Outcome: Is all that stuff really supposed to go in all my different Controller methods.

PERTAIN_TOSolution

You could write a Service class that handles and simplifies the syntax for starting and stopping Sentry transactions and spans. — Create a `app/Services/SentryMeasureService.php`. Tension: starting and stopping Sentry transactions and spans. Outcome: You could write a Service class.

PERTAIN_TOProblem

What's the difference between OpenTelemetry and Sentry? — At first glance they look similar with regarding to tracing, logs etc. Tension: However, there should difference between them. Outcome: Sentry is a product, with proprietary SDKs you can use in your application to generate telemetry.

PERTAIN_TOSolution

OpenTelemetry is a set of tools and standards to generate telemetry to send to any vendor — including Sentry. Tension: there is no proprietary code in your application. Outcome: that allow you to switch vendors easily since there is no proprietary code in your application.

PERTAIN_TOSolution

use the `ignoreErrors` option — https://docs.sentry.io/platforms/javascript/configuration/filtering/. Tension: Sentry.init({ ignoreErrors: [ "Can't find variable: gmo" ], });. Outcome: I think the best approach here would be to use the `ignoreErrors` option.

PERTAIN_TOProblem

it does not have any information about the traceback as seen in the R console — if shiny is connected with the sentryR R package for reporting the errors on sentry dashboard. Tension: The only info about the error is in Message. Outcome: I want to capture the full traceback.

PERTAIN_TOSolution

The key is to use `shiny::printStackTrace`. — This was answered by Tan Ho on DSLC slack. Tension: it does not have any information about the traceback as seen in the R console. Outcome: This produces the exact same traceback on sentry dashboard that is seen in the R console.

PERTAIN_TOSolution

Sentry.configureScope( (scope) => scope.setUser(SentryUser(id: '1234', email: 'jane.doe@example.com')), ); — Basically you can configure the scope like this. Tension: If this is not working for you maybe a try/catch block can help you, or even log something to the console. Outcome: scope.setUser(SentryUser(id: '1234', email: 'jane.doe@example.com')).

PERTAIN_TOProblem

Unable to identify whether Sentry event data is APM/transaction data in BeforeSend/BeforeSendTransaction

PERTAIN_TOSolution

Set TracesSampleRate = 0 and ensure EnableTracing is false to stop sending APM messages

PERTAIN_TOSolution

Use BeforeSendTransaction to drop transactions by returning null

PERTAIN_TORootCause

Sentry's LoggingIntegration itself is effectively a third handler — messages passing through the logging system. Tension: which handler will be used by sentry to display an error message ? Outcome: filter them by log level based on the configuration of Sentry's LoggingIntegration.

PERTAIN_TOProblem

Sentry logging integration ignores the logs from some libraries or frameworks — By default. Tension: you may need to manually enable their inclusion. Outcome: the integration examples for various frameworks show you how to enable all the usually needed loggers.

PERTAIN_TOProblem

which handler will be used by sentry to display an error message ? — So if there are 2 handlers to a logger. Tension: I want to custom format the output thats sent to sentry. Outcome: Neither.

PERTAIN_TOSolution

Sentry's LoggingIntegration itself is effectively a third handler which does its own thing. — Depending on which framework(s) you're using. Tension: By default, Sentry logging integration ignores the logs from some libraries or frameworks. Outcome: you may need to manually enable their inclusion.

PERTAIN_TOProblem

it harder to track down real issues.

PERTAIN_TOProblem

if our app suddenly produces a new 400 error that we haven't seen before — Exception Types by Count. Outcome: we need to dete ct and get alerted about it.

PERTAIN_TOSolution

And HTTP Client errors (if you're using `HttpClient` or `HttpClientFactory`) — On ASP.NET Core. Tension: you just need to opt-in. Outcome: options.CaptureFailedRequests = true;.

PERTAIN_TOSolution

alerts you on new issues — It aggregates events with fingerprint (by default based on stack trace) into 'issues'. Tension: focused on capturing the most amount of types of errors your app can have. Outcome: You can configure alerts of course for other conditions beyond new issues.

PERTAIN_TOSolution

report them with extensive context that can help you debug what's going on — Including lines of code but also surrounding source code, even if PDBs are not shipped with the final app. Tension: even if PDBs are not shipped with the final app. Outcome: Sentry's SDK has an msbuild task that can upload PDBs to Sentry for server-side symbolication.

PERTAIN_TOProblem

I could not find any examples on how to do it — using the Sentry SDK for Rust. Tension: The official documentation lacks any mention of SDK fingerprinting. Outcome: found this example directly from the sentry-rust repository.

PERTAIN_TOProblem

the server returns `Grpc.Core.RpcException` for ALL exceptions — We are using Sentry to monitor errors/issues on the ASP.NET Core gRPC service. Tension: In Sentry, we have just one issue with hundreds of different error. Outcome: we want to split this somehow.

PERTAIN_TOProblem

it just creates another attribute with the same name — Span names from the documentation list: https://develop.sentry.dev/sdk/performance/span-operations/. Tension: I tried to specify through an attribute.

PERTAIN_TOSolution

ctx, span := trace.Tracer.Start(ctx, "name", trace.WithAttributes(attribute.String("faas.trigger", "http.server"))) defer span.End() — OpenTelemetry package of the Go language. Tension: Span names from the documentation list: https://develop.sentry.dev/sdk/performance/span-operations/.

PERTAIN_TOProblem

I tried clearing `excluded_exceptions` in `sentry.rb` initializer file, but this had no effect: — Sentry.init do |config|. Tension: How can I configure Sentry so that these are sent as errors? Outcome: I was also thinking that I can modify the middleware.

PERTAIN_TOProblem

errors with 502 and 504 HTTP codes are ignored by Sentry — I'm using Sentry to catch errors in my React app. Tension: some React errors are ignored too. Outcome: I'd like to override this behavior.

PERTAIN_TOProblem

I set the traces sample rate to 0.0 so as to stop the transactions being published to sentry — in the spring boot application. Tension: We would be using sentry for error reporting but not for performance monitoring.

PERTAIN_TOProblem

Tension: When I run it on dev server again but with extended events capturing (or profiler trace) running, it runs slowly just like prod. Outcome: If I pause the trace, it's immediately fast again.

PERTAIN_TOSolution

Simply turning off the monitoring (the SQL trace) on production decreased a prod script from 8 minutes to 40 seconds — If monitoring is still required (for auditing or other reasons). Outcome: there is a workaround provided by @gordthompson which uses OPENJSON.

PERTAIN_TOProblem

send performance transactions to Sentry using a Ktor server plugin — using a Ktor server plugin to track performance metrics for API calls. Tension: How can I integrate the Sentry java and kotlin SDKs with Ktor?

PERTAIN_TOSolution

send performance transactions to Sentry using a Ktor server plugin — How can I integrate the Sentry java and kotlin SDKs with Ktor?

PERTAIN_TOSolution

you will then need to configure the Sentry SDK to export the OpenTelemetry traces to Sentry — Once you have OpenTelemetry traces and spans being generated following the Quarkus documentation you linked.

PERTAIN_TOSolution

Each route with a decorator are registred in a dictionary with their trace/error rate — I then used a trace_sampler/before_send function as indicated here. Tension: I finally managed to do it using a registry mechanism. Outcome: Each route with a decorator are registred in a dictionary with their trace/error rate. I then used a trace_sampler/before_send function as indicated here.

PERTAIN_TOProblem

the health check is filling all the Sentry transaction limits — I have a Django application with a health check endpoint that's using django-health-check. Tension: How can I exclude the health check endpoint in Sentry? Outcome: use a sampling function to control the sample rate according to the URL or other parameters.

PERTAIN_TOSolution

if url.startswith('/ht/'): return 0 # Don't trace any of these transactions — sentry_sdk.init( # ... traces_sampler=traces_sampler, ). Tension: the health check is filling all the Sentry transaction limits. Outcome: return 0.1 # Trace 10% of other transactions.

PERTAIN_TOProblem

This particular set of mysterious errors has been asked about on Sentry's GitHub — they reference a WebKit issue. Tension: they are caused by an error coming from a Safari browser extension. Outcome: can safely be ignored, or filtered.

PERTAIN_TOSolution

can safely be ignored, or filtered — According to the comments there. Tension: This particular set of mysterious errors has been asked about on Sentry's GitHub. Outcome: can safely be ignored, or filtered.

PERTAIN_TOProblem

However the `BeforeSend` is a — I'm trying to use Sentry.AspNetCore (3.22.0) in a AspNetCore Api, but need to filter certain endpoints and events. Tension: I understand the way to do this is to return a null in BeforeSend, however I cannot get this to trigger at all. Outcome: Both the calls to `.AddSentry` are being hit.

PERTAIN_TOProblem

sentry-sdk sends every raised CustomError to the DSN

PERTAIN_TOSolution

Use before_send to inspect hint['exc_info'] and return None for CustomError instances

PERTAIN_TOSolution

when you capture exception, add transactionName to `scope`. Tension: you can also enhance event in `beforeSend` method. Outcome: scope.setTransactionName(`my custom title for error`);.

PERTAIN_TOProblem

Every curl error is sent to Sentry. — There is a Job that works just fine 99% of time. It retries N times. Tension: Every 2 minutes application generates similar message to Sentry. Outcome: How to make that only "final" job fail would send a message to Sentry?

PERTAIN_TOSolution

you should be able to handle the error and replicate the behavior of the framework by using `$this->release()` — When the number of attempts made is less than the tries. Outcome: re-throwing the exception should cause it to send to your error reporting system and fail the job as expected.

PERTAIN_TOProblem

Safari DevTools console shows full details, but JS code only gets "TypeError: Load failed"

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

Instrumentation - inErrata Knowledge Graph | Inerrata