Summary
This is an emergency release to ensure Metrics utility raises an exception when customers add 9 user-defined metric dimensions.
Huge thanks to @dnlopes for spotting this bug thus warranting this emergency release.
Background
Lambda Powertools adds a service CloudWatch Metric Dimension on top of user-defined dimensions (max 8). Prior to this release, customers were able to add 9 user-defined dimensions leading to a total of 10 metric dimensions. This makes CloudWatch EMF fail silently and not convert them as metrics.
The confusion stems from CloudWatch Metrics and CloudWatch Logs EMF having different limits. CloudWatch Metrics support 10 dimensions while CloudWatch EMF (async) support 9. For EMF, all validation must happen client side as EMF fails silently should any limit is hit and no feedback is given.
We provided this feedback to the CloudWatch EMF team, and they're looking at ways to improve customers feedback on the server-side so it's less reliant on client-side validation.
Changes
📜 Documentation updates
- fix(metrics): raise SchemaValidationError for >8 metric dimensions (#1240) by @heitorlessa
- docs(maintainers): initial maintainers playbook (#1222) by @heitorlessa
🐛 Bug and hot fixes
- fix(metrics): raise SchemaValidationError for >8 metric dimensions (#1240) by @heitorlessa
🔧 Maintenance
- docs(maintainers): initial maintainers playbook (#1222) by @heitorlessa
- chore(deps-dev): bump mypy from 0.950 to 0.960 (#1224) by @dependabot
- chore(deps-dev): bump mypy-boto3-secretsmanager from 1.23.0.post1 to 1.23.8 (#1225) by @dependabot
This release was made possible by the following contributors:
@dependabot, @dependabot[bot] and @heitorlessa