-
Notifications
You must be signed in to change notification settings - Fork 66
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
parse_multiline no longer working (worked in legacy agent) #1518
Comments
Here is another exception that does not get processed into 1 line:
|
Lines 68 to 90 in f38c005
|
|
I am not quite understanding what it doesn't like about the first line
that causes it to not honor I wish there was better documentation. |
Hey @codeconsole, Thanks for reporting the issue. I tried to reproduce this on my side with this config:
The first exception got parsed correctly into one log:
The second exception was not combined, but sent as three individual logs. It is probably caused by the second line:
is not normally expected and did not get matched by any of the It would work if the second exception is
To further assist with this issue and to help us reproduce on our side:
Thanks! |
Ever since upgrading from the legacy agent, I have not been able to get multiline exception parsing to work. The exception appears in the logs line by line instead of being grouped into an individual entry.
Sample log entry:
I followed the documentation here
Why isn't able to capture that exception? Is the formatting very specific or something?
Is there documentation on the exact format it is looking for?
The text was updated successfully, but these errors were encountered: