-
Notifications
You must be signed in to change notification settings - Fork 32
🐛 fix Graylog parsing issue #8191
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
🐛 fix Graylog parsing issue #8191
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8191 +/- ##
==========================================
- Coverage 88.04% 87.97% -0.07%
==========================================
Files 1907 1483 -424
Lines 73282 60849 -12433
Branches 1302 651 -651
==========================================
- Hits 64519 53531 -10988
+ Misses 8374 7089 -1285
+ Partials 389 229 -160
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
pcrespov
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.
greatly appreciated! BIG RoI in here!
bisgaard-itis
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.
Very nice! Thanks a lot for the effort.
|
@mergify queue |
🟠 Waiting for conditions to match
|
|
8e85054
into
ITISFoundation:master



What do these changes do?
Noneas the default value when OpenTelemetry tracking is disabled. I've also added unit tests that will fail if the format changes, making it clear that the corresponding Grok pattern in Graylog must be updated.Related issue/s
How to test
packages/service-library/tests/test_logging_utils.py
Dev-ops