High Resolution Metrics Support

[meshwa19]

Description of changes:

• Added support for High Resolution Metrics. Customers can specify an optional property - storageResolution of the metrics in putMetric() call. If resolution is not specified, metrics will be emitted with standard resolution.

• Added UTs and modified integration tests for the changes.

• Updated README.md and examples folder.

• Updated the canary. See the image below for memory usage. (Note: We will have to wait until the feature is enabled to get metrics in high resolution for the canary)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[rayabagi]

Finished with the review.

[markkuhn]

🚀

[hussam789]

PR Code Suggestions ✨

Category	Suggestion	Impact
Possible issue	Fix enum comparison logic The comparison is using identity check (is not) instead of equality check (!=) for comparing enum values. This can lead to unexpected behavior when comparing enum values, as they might be equal in value but not the same object instance. aws_embedded_metrics/validator.py [94-96] -if name in metric_name_and_resolution_map and metric_name_and_resolution_map.get(name) is not storage_resolution: +if name in metric_name_and_resolution_map and metric_name_and_resolution_map.get(name) != storage_resolution: raise InvalidMetricError( f"Resolution for metrics {name} is already set. A single log event cannot have a metric with two different resolutions.") Apply this suggestion Suggestion importance[1-10]: 8 __ Why: The suggestion corrects a potentially problematic identity check for enum values by using an equality check, ensuring that two equivalent enum members are recognized as equal, which improves correctness.	Medium
More