Home Search Pricing Get inErrata About

Sign in Sign up

Graph/instrumentation-sampling-exclusion-by-url

Pattern

Instrumentation Sampling Exclusion

instrumentation-sampling-exclusion-by-url

A recurring observability motif where instrumentation is conditionally suppressed or reduced for specific request/URL paths, to prevent low-value endpoints (like health checks) from consuming transaction limits or noise in trace data.

Node Details

Public graph metadata

Updated4/30/2026

Connections

30 linked nodes

previous in-flight requests are not cancelled by `injectQuery` — Angular 18 with TanStack Angular Query. Outcome: I searched for a possible workaround, but did not find any.

the data will Suspend and get fetched on the server but never be hydrated to the client — If you do forget to prefetch a query when you are using useSuspenseQuery. Tension: the consequences will depend on the framework you are using.

useSearchParams(); — during client rendering. Tension: can suspend during client rendering.

This is treated by Sentry as an error and being logged into Sentry. — I have some cases in which I am cancelling the token for certain API requests. Tension: I would like cancel token errors to not be logged. Outcome: This has not worked.

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.

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.

there are some exceptions where useless to report — monitor our Shopware 6 shops. Tension: we want to collect exception classes which are safe to ignore. Outcome: It's up to everyone on their own if they ignore those exceptions in Sentry themselves.

such as the entry of a wrong password or wrong CSRF tokens. Tension: more an user error than a system error or caused by spam bots. Outcome: collect exception classes which are safe to ignore.

there are no typing for `sampling_context` variable — how to use with FastAPI. Tension: I have no idea how to filter specific http route in case of FastAPI integration. Outcome: set different sample rate for specific route.

I want to disable EB health check entries. — I've set up entry in a django project. Tension: I tried to do it with middleware like this. Outcome: It can be done by `traces_sampler`.

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.

the response headers from the FastAPI service don't have the `x-b3-spanid` and `x-b3-traceid` response headers — trying to get auto instrumentation working for a FastAPI service. Tension: but not having any luck.

trying to perform data processing during the application's startup. Tension: This limitation forces me to manually create instances of these dependencies. Outcome: this approach doesn't work as expected.

runs-on: [self-hosted, devops ] — I have a github action that runs on self-hosted runners. Tension: there is no runner like this in our org. Outcome: There's no direct way to exclude labels in `runs-on`.

Testing (onboarding new accounts). Tension: However (whether using the API, or creating user from within the dashboard), created accounts are 'restricted' and useless to use for testing payments on_behalf_of etc etc. Outcome: As far as functionality goes, test mode operations should work despite the accounts being in a restricted status.

Repeating the name with each sample. Tension: an extremely inefficient use of space. Outcome: results in an order of magnitude improvement in storage efficiency.

Filter rows from a table so that records with sensorfield1 flag = 'r' are selected, except for IDs that have corresponding rows with flag = 'h'; for IDs where flag value is only 'h', include those rows as well. Denodo throws an error when attempting a solution using analytic/window functions: '(function) is not executable'.

Allowing users to upload and embed their own web components as dashboard widgets, while preventing them from accessing cookies or other data on the hosting page without manually auditing each widget.

traditional browser fingerprinting methods aren't revealing any unusual characteristics or anomalies. Tension: CDP-controlled browsers mimic regular user browsers closely. Outcome: no general answer which applies long-term to this question.

Each application should gets its own token for data access. Tension: with its own access to resources.

Avoid passing tokens in URLs. Tension: tokens can leak to logs and be exploited.

In a large npm codebase, polyfill.io usage is hard to detect reliably because simple greps and manual network inspection can miss dynamically loaded polyfills or subdependencies.

but still 401. Tension: i`m trying to configure prometheus in my app with springSecurity. Outcome: The default is: /actuator/**.

The user wants to completely hide port 80 from external port scanners for an Azure WebApp that currently serves HTTPS-only.

trigger programs, check constraints, view definitions, etc. — if the new function has side effects or reveals internal state about the application and the -directonly option is not used. Tension: the application into running the function with parameters of the attacker's choosing. Outcome: Marking a function as direct only disqualifies it from being run in those situations.

authorization code injection attacks against confidential clients

String predicate handling still allows arbitrary SQL and information disclosure

the Internal service is by accident exposed to the outside world — The Internal service is on a network-level not exposed to the outside world. Tension: users could then make changes to the Internal service that should not be allowed.

The Heroku-hosted MERN app receives many automated-looking requests from the same forwarded IP in the same second, with suspicious query/path content (e.g., unexpected “if”/“php” strings). This behavior appears to be scanning or an attack proxy and raises concerns about security and abuse.

GET API calls for improved security. Tension: I have many parameters and I could check each input value manually but that seems like an uphill battle and would also impact application performance.

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

© 2026 Inerrata

Instrumentation Sampling Exclusion - inErrata Knowledge Graph | Inerrata