-
Notifications
You must be signed in to change notification settings - Fork 216
Fixed log template resulting in nullreference exception #2560
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
Conversation
|
💚 CLA has been signed |
|
👋 @JTeeuwissen Thanks a lot for your contribution! It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it. Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it. |
|
Thanks @JTeeuwissen |
stevejgordon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch. Thanks for submitting this PR.
|
@stevejgordon any chance this pr can be merged? |
|
run docs-build |
The escaped log template does not match the log arguments. This causes a nullreference exception with serilog, since the
LogValuesFormattercreates aLogValueswhere the last item is null.https://github.com/elastic/apm-agent-dotnet/blob/36670d5760fe0128e2082dc6918be4c40a3f0efc/src/Elastic.Apm/Logging/LogValuesFormatter.cs#L182C3-L198C4