You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
For some logged exceptions, it is projecting the objects fields we pass as additional information and parsing them into custom fields. This was not normally an issue where we have used the same practice elsewhere. Rather than creating one custom field that is then used repeatedly it appears to be creating multiple fields every time the exception is logged. However we have been unable to find the log that is causing this issue insofar.
To Reproduce
Steps to reproduce the behavior:
Unknown
Expected behavior
Unsure if this is intended behaviour, however some guidance on why you would believe this is happening would be appreciated.
Screenshots
Additional context
Below is more or less how we have extended the Logger interface.
The text was updated successfully, but these errors were encountered:
Describe the bug
For some logged exceptions, it is projecting the objects fields we pass as additional information and parsing them into custom fields. This was not normally an issue where we have used the same practice elsewhere. Rather than creating one custom field that is then used repeatedly it appears to be creating multiple fields every time the exception is logged. However we have been unable to find the log that is causing this issue insofar.
To Reproduce
Steps to reproduce the behavior:
Unknown
Expected behavior
Unsure if this is intended behaviour, however some guidance on why you would believe this is happening would be appreciated.
Screenshots
Additional context
Below is more or less how we have extended the Logger interface.
The text was updated successfully, but these errors were encountered: