Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
cijothomas opened this issue Jul 28, 2023 · 1 comment
Closed

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

cijothomas opened this issue Jul 28, 2023 · 1 comment
Assignees
Labels
A-common Area:common issues that not related to specific pillar priority:p1 Critical issues and bugs. Highest priority. triage:accepted Has been triaged and accepted. version:minor Tag PR which would make sense to bump the "minor" in semver. https://semver.org/

Comments

@cijothomas
Copy link
Member

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.

@TommyCpp TommyCpp added A-common Area:common issues that not related to specific pillar priority:p1 Critical issues and bugs. Highest priority. triage:accepted Has been triaged and accepted. version:minor Tag PR which would make sense to bump the "minor" in semver. https://semver.org/ labels Aug 8, 2023
@cijothomas
Copy link
Member Author

cijothomas commented Oct 24, 2023

Closing as duplicate #761

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-common Area:common issues that not related to specific pillar priority:p1 Critical issues and bugs. Highest priority. triage:accepted Has been triaged and accepted. version:minor Tag PR which would make sense to bump the "minor" in semver. https://semver.org/
Projects
None yet
3 participants