-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/loki] Documentation incorrect on mapping severity to level #31333
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@mar4uk, do you remember if this was changed from the original implementation? |
Sorry if this is obvious, but what's the difference from the code vs. documentation? From my understanding of the OTLP log spec, severity would be the Is the expectation from documentation that the exporter should actually be getting the severity from a different field in a log that's explicitly named For context, it looks like this functionality along with the README comment came in the same change. |
@crobert-1, indeed, the goal is to correct the documentation on the mapping. |
Okay, thanks for the clarification! I didn't know there was an understanding that |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Fixes open-telemetry#31333 Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Component(s)
exporter/loki
Describe the issue you're reporting
The Loki exporter documentation states that the
record.severity
is mapping torecord.attributes.level
(used by Loki) but it appears that it is the severityNumber which is used for the mapping (code reference)The text was updated successfully, but these errors were encountered: