Skip to content

Need a way to suppress telemetry from SDKs own operation #1171

Closed
@cijothomas

Description

@cijothomas

There is no mechanism today to suppress telemetry arising from SDK's own operations. For example, OTLP Exporter uses tonic, which is instrumented with tracing crate. When one enables tracing-appender, along with OTLP Exporter, all the logs emitted by tonic inside OTLPExporter, gets routed to OpenTelemetry! This is a never ending "live loop", as every export cause logs to be produced, which causes export to occur again, which further creates logs again and so on.

There was never a spec written for this (open-telemetry/opentelemetry-specification#530), but languages like Python, .NET had provided solutions for this.

Opening an issue to track adding a capability to "Suppress instrumentation" in OTel Rust SDK, and have the official exporters leverage it.

Metadata

Metadata

Assignees

Labels

A-commonArea:common issues that not related to specific pillarpriority:p1Critical issues and bugs. Highest priority.triage:acceptedHas been triaged and accepted.version:minorTag PR which would make sense to bump the "minor" in semver. https://semver.org/

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions