Skip to content

Conversation

@cavis
Copy link
Member

@cavis cavis commented Jan 13, 2026

Deploying the stream-recorder lambda.

@cavis cavis requested a review from farski January 13, 2026 18:49
StreamRecorderFunctionWarnLevelLogMetricFilter:
Type: AWS::Logs::MetricFilter
Properties:
FilterPattern: '{ $._logLevel = "warn" }'
Copy link
Member

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.

Copy link
Member Author

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct

Copy link
Member Author

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

@cavis cavis requested a review from farski January 14, 2026 16:42
@cavis cavis merged commit 3f5f820 into main Jan 14, 2026
4 checks passed
@cavis cavis deleted the feat/stream_recorder branch January 14, 2026 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants