-
Notifications
You must be signed in to change notification settings - Fork 11
Setup stream recorder lambda #873
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
Conversation
| StreamRecorderFunctionWarnLevelLogMetricFilter: | ||
| Type: AWS::Logs::MetricFilter | ||
| Properties: | ||
| FilterPattern: '{ $._logLevel = "warn" }' |
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.
I know there's prior art for these log-level-based alarms, but I always sort of wonder why we don't just emit specific CloudWatch metrics and alarm on those. If things are getting to a point in the code where we are able to decide to log warn vs. error, we probably can equally decide what metric/value to publish, and then these alarms become a lot more meaningful.
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.
"Emit metrics" meaning... via the aws sdk?
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.
Correct
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.
I guess the downsides are:
- One more dependency to install, permission, and stub out in the tests
- I'd still want the log output anyways, even if we also directly send the CW event
Deploying the stream-recorder lambda.