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.

Sign up for GitHub

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

Jump to bottom

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

Closed
cijothomas opened this issue Jul 28, 2023 · 1 comment · May be fixed by #1330
Closed

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

cijothomas opened this issue Jul 28, 2023 · 1 comment · May be fixed by #1330
Assignees
@lalitb
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.
@cijothomas cijothomas mentioned this issue Jul 28, 2023
Merged
@cijothomas cijothomas mentioned this issue Aug 7, 2023
Open
@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 cijothomas mentioned this issue Sep 13, 2023
Merged
2 tasks
@lalitb lalitb mentioned this issue Oct 12, 2023
Merged
4 tasks
@lalitb lalitb mentioned this issue Oct 24, 2023
Closed
4 tasks
@cijothomas
Copy link
Member Author

cijothomas commented Oct 24, 2023 •
edited

Closing as duplicate #761

@lalitb lalitb mentioned this issue Nov 1, 2023
Draft
@cijothomas cijothomas mentioned this issue Apr 28, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lalitb lalitb

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
Milestone
No milestone
3 participants
@lalitb @cijothomas @TommyCpp