-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Filelog severity_parser operator does not set severity_text correctly #35049
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
#26671 may do just what you need. |
Thanks @djaglowski! Indeed that
Seems it's missing from the docs. Regardless, I'll close this issue as my problem is solved (the severity text is now being set correctly). Cheers :) |
I've opened #35074 to address the missing documentation. Thanks for calling this out @perry-mitchell. |
Component(s)
receiver/filelog
What happened?
Description
I'm trying to use the
severity_parser
to parse the log stream, eitherstdout
orstderr
to set severity. It sets theseverity_number
correctly but theseverity_text
value becomesstdout
orstderr
, notINFO
orERROR
as I'd expect.Steps to Reproduce
Use the following severity parser (HCL format sorry):
Expected Result
Mentioned above - correct
severity_text
Actual Result
Logs like this:
Collector version
0.101.1
Environment information
Environment
OS: Docker - Helm chart on Kubernetes
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: