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

Appender-Tracing - handle target and scope #2658

Open
cijothomas opened this issue Feb 13, 2025 · 0 comments
Open

Appender-Tracing - handle target and scope #2658

cijothomas opened this issue Feb 13, 2025 · 0 comments

Comments

@cijothomas
Copy link
Member

#1683 this stored target in a top level field and have OTLP Exporter treat it as scope.

The tracing-appender information is totally lost now.
open-telemetry/semantic-conventions#1550 proposes to store this in scope attributes. Need to follow up.

Additionally, register_callsite may be overridden to get the target name once for every callsite instead of every invocation. This may be leveraged to maintain a Map of Loggers per target. (This will cause contention, or need to use thread-local map!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant