Disable Instrumentation for Some Endpoints #614
Replies: 2 comments 6 replies
-
same issue here.
|
Beta Was this translation helpful? Give feedback.
-
Hi there, Unfortunately, this isn't currently configurable in Orchestrion. However, the team plans to bring integration-level configuration—like what's available in dd-trace-go via manual instrumentation—to Orchestrion soon. In the meantime, you can use sampling rules to prevent traces from this endpoint from being ingested. See: https://docs.datadoghq.com/tracing/trace_pipeline/ingestion_mechanisms/?tab=go#in-tracing-libraries-user-defined-rules You can set the following environment variable on your service: Or via programmatic configuration:
More information here: https://pkg.go.dev/github.com/DataDog/dd-trace-go/v2@v2.0.1/ddtrace/tracer If you are unfamiliar with ingestion, these docs are a good place to start:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I might be missing something in the documentation, but I've been trying to find a way to disable instrumentation for some endpoints when building with
orchestrion
and I can't find a way. Specifically, the/ready
endpoint, which our load balancer uses, spams the trace logs because it's being called multiple times per second.Using manual instrumentation, I think I could do something like this:
However, I can't seem to find a way to use any of the
chitrace
configuration functions (or, for that matter, those of any other tracer library) when I'm usingorchestrion
. Did I miss something in the docs or is what I'm trying to do not possible?EDIT: My team has also pointed out that we've tried this in the endpoint handler, which doesn't seem to stop the traces to the
/ready
endpoint:Beta Was this translation helpful? Give feedback.
All reactions