-
Notifications
You must be signed in to change notification settings - Fork 99
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
Exception thrown when detect_exceptions
filter is not being used
#339
Labels
bug
Something isn't working
Comments
@javiercri does this make sense at all? Am I understanding things correctly? As you can see in NewRelic: it's just empty messages :) |
Running in kubernetes, collecting log files in the container, application services with json logs and multi-line logs, how can I be compatible with this plug-in to support hot update Only by adding the following configuration can json logs and multi-line logs be recognized normally
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This is not so much a bug as it is an ask for how things are supposed to behave. We don't have
detect_exceptions
filter added but within our logs we have stacktraces dumped in between our json logs. When these logs eventually make their way over to NewRelic we see a lot of logs wherestream: stderr
but there is nomessage
field present. There are also loads of these dumped seemingly at the same time.Is this the expected behavior when the operator encounters a stacktrace and doesn't know what to do with it? Meaning it just creates a
stream: stderr
log with nomessage
injected? That seems l suppose logical just want to confirm.FWIW: we haven't enabled the
detect_exceptions
filter due to this currently open bug from over a year ago. We're not sure if this is still an issue with recent versions as we haven't tested but it's at least why we haven't tried it again.Reproduction steps
Default behavior when `detect_exceptions` is not enabled but exceptions are encountered.
Expected behavior
Not sure actually which is why I'm here :)
Additional context
No response
The text was updated successfully, but these errors were encountered: