Optionally send Error-level logs to Cloud Error Reporting #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
GCP Cloud Error Reporting aggregates application errors by root cause. It automatically scans Cloud Logging messages for anything that looks like an exception with a stack trace, but sometimes we want it to recognize error logs as well. Google supports this by setting the
@typeproperty of the log to a specific value.This PR adds a new parameter that, when enabled, will cause the formatter to set the
@typeto this value for any log with a level of Error or higher. These logs will then be processed by Cloud Error Reporting.Error Reporting overview:
https://cloud.google.com/error-reporting/docs/grouping-errors
Log Formatting documentation:
https://cloud.google.com/error-reporting/docs/formatting-error-messages#log-text