-
Notifications
You must be signed in to change notification settings - Fork 239
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
chore: Ensure we use structured logging when returning disruption commands #1998
chore: Ensure we use structured logging when returning disruption commands #1998
Conversation
Skipping CI for Draft Pull Request. |
Pull Request Test Coverage Report for Build 13442769211Details
💛 - Coveralls |
2542084
to
84d0971
Compare
84d0971
to
a579ac3
Compare
a579ac3
to
7a90cc7
Compare
7a90cc7
to
b6860c0
Compare
b6860c0
to
2be6773
Compare
2be6773
to
a478230
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jonathan-innis, rschalo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #N/A
Description
This change moves all of the structured data that was previously in the disruption message into actual structured fields. This should make it easier to parse data when using logging solutions that automatically parse-out JSON keys
Before Change
After Change
How was this change tested?
make presubmit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.