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

Logs: Instrumentation Scope for logs not from LoggerProvider provided Logger #2833

Open
tsloughter opened this issue Sep 23, 2022 · 0 comments
Assignees
Labels
[label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR spec:logs Related to the specification/logs directory

Comments

@tsloughter
Copy link
Member

What are you trying to achieve?

Implementing the Logs SDK and need to export logs emitted by the language's structured logger.

Additional context.

Since exporting logs through OTLP requires a Scope which the log records are under and not all logs emitted by a program will be within an Instrumentation Scope, how is exporting these logs to be done?

In my case I have planned to use the library name and version the log comes from to create a Scope, but there are times (such as a log generated in the REPL) that no such information is available and I assume others are in a similar situation.

Is using information like library name/version to create a Scope a strategy that should be suggested in the spec?

And where no such information is available should an empty string name and version be used for a Scope?

@tsloughter tsloughter added the spec:logs Related to the specification/logs directory label Sep 23, 2022
@rbailey7210 rbailey7210 added the [label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR label Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[label deprecated] triaged-accepted [label deprecated] Issue triaged and accepted by OTel community, can proceed with creating a PR spec:logs Related to the specification/logs directory
Projects
None yet
Development

No branches or pull requests

3 participants