Skip to content

fix(metrics): align flush_metrics behavior with raise_on_empty_metrics documentation #7468

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
+1 −1
Open

fix(metrics): align flush_metrics behavior with raise_on_empty_metrics documentation #7468

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d34dead
https://github.com/aws-powertools/powertools-lambda-python/blob/adbd9…
jotafeldmann Oct 2, 2025
becaa4f
Merge branch 'develop' into patch-1
leandrodamascena Oct 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aws_lambda_powertools/metrics/provider/cloudwatch_emf/cloudwatch.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -390,7 +390,7 @@ def flush_metrics(self, raise_on_empty_metrics: bool = False) -> None:
raise_on_empty_metrics : bool, optional
raise exception if no metrics are emitted, by default False
"""
if not raise_on_empty_metrics and not self.metric_set:
if not raise_on_empty_metrics:
warnings.warn(
"No application metrics to publish. The cold-start metric may be published if enabled. "
"If application metrics should never be empty, consider using 'raise_on_empty_metrics'",
Expand Down
Loading