[batch] Add json parsing and severity to GCP Ops Agent config #14187
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the Ops Agent does not do any parsing of the log message, so the log entry in Google Logging looks like:
The
parse_json
processor extracts the json fields from the message into fields on thejsonPayload
so it looks like thisand only the new
message
field is displayed in the Google Logging row instead of the whole json.This also adds a
severity
field on the log entry so filters such asSEVERITY!=INFO
work as expected.