fix: add additional severity field to stackdriver #194
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.
The
logging.googleapis.com/severity
field is no longer mentioned in https://cloud.google.com/logging/docs/agent/configuration#special-fields docs, and when viewed in Google Cloud Logging, severity is missing (and inferred from stderr as ERROR).For this reason, we add the
severity
field as well. Thelogging.googleapis.com/severity
field is still mentioned in https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/configuration#special-fields, which is why we keep it.An example configuration on that page suggests rewriting the field (https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/configuration#example_configuration_2), however, this seemed cumbersome to do in our deployment on
big.cdr.dev
and sending both fields seems like a good compromise.