-
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
[pkg/stanza] Operators configured with Silent Errors would still result in error logs #35008
Labels
bug
Something isn't working
needs triage
New item requiring triage
pkg/stanza/fileconsumer
pkg/stanza
receiver/filelog
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
djaglowski
pushed a commit
that referenced
this issue
Sep 6, 2024
…n an error (#35010) An operator configured with silent errors shouldn't log errors while processing log entries. **Description:** Operators that are expected to sometimes fail, can result in error logs that are quite verbose. This aims to address this issue by getting rid of error logs that the user wishes to silence (debug logs instead). By making sure no error is returned, there won't be any need to worry about other components logging error logs. **Link to tracking Issue:** [Issue #35008](#35008) **Testing:** Manually tested as this is a matter of logs.
f7o
pushed a commit
to f7o/opentelemetry-collector-contrib
that referenced
this issue
Sep 12, 2024
…n an error (open-telemetry#35010) An operator configured with silent errors shouldn't log errors while processing log entries. **Description:** Operators that are expected to sometimes fail, can result in error logs that are quite verbose. This aims to address this issue by getting rid of error logs that the user wishes to silence (debug logs instead). By making sure no error is returned, there won't be any need to worry about other components logging error logs. **Link to tracking Issue:** [Issue open-telemetry#35008](open-telemetry#35008) **Testing:** Manually tested as this is a matter of logs.
jriguera
pushed a commit
to springernature/opentelemetry-collector-contrib
that referenced
this issue
Oct 4, 2024
…n an error (open-telemetry#35010) An operator configured with silent errors shouldn't log errors while processing log entries. **Description:** Operators that are expected to sometimes fail, can result in error logs that are quite verbose. This aims to address this issue by getting rid of error logs that the user wishes to silence (debug logs instead). By making sure no error is returned, there won't be any need to worry about other components logging error logs. **Link to tracking Issue:** [Issue open-telemetry#35008](open-telemetry#35008) **Testing:** Manually tested as this is a matter of logs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
needs triage
New item requiring triage
pkg/stanza/fileconsumer
pkg/stanza
receiver/filelog
Component(s)
pkg/stanza, pkg/stanza/fileconsumer, receiver/filelog
What happened?
Description
Operators have a config that allow silencing errors logs (log level is changed from error to debug).
With this configuration, we expect no error logs when the operator fails to process a log entry.
However, even when we use
drop_quiet
, we still see error logs when the Operator fails.The error is not emitted by the Operator but by another component. Nevertheless, the error is because of the operator's log entry failure.
Steps to Reproduce
Use any operator, that might sometimes fails like regex with a pattern that might not always match.
Set the property
on_error: drop_quiet
.Feed the operator log entries were some are expected to fail the operator.
Check the emitted logs.
Expected Result
No errors logs when it comes to failures by the Operator
Comparison
You can see that with quiet we hide some of the error logs but not all.
Default
Quiet
Collector version
0.107.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: