Skip to content
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

[metrics]: Missing spike points in metrics collected for aws_metric_name ThreatsFound #712

Open
sushovan23 opened this issue Aug 2, 2024 · 0 comments
Labels
metrics-configuration How to configure specific metrics for collection

Comments

@sushovan23
Copy link

sushovan23 commented Aug 2, 2024

Context information

  • AWS service: aws_metric_name: ThreatsFound
  • CloudWatch namespace: aws_namespace : UTM-Alerting-Metrics
    aws_statistics: Sum
  • Link to metrics documentation for this service:
  • AWS region of the exporter:
  • AWS region of the service:
Exporter configuration
</summary>
 aws_dimentions: []
       aws_namespace: UTM-Alerting-Metrics
       aws_statistics:
       - Sum

Exporter logs

What do you expect to happen?

When there is spike in metrics we can see them in cloudwatch metrics in AWS console but not in prometheus query.
It gets data but misses the short spikes

What happened instead?

exporter is not able to catch the spike in metric data which we can see in cloudwatch but in prometheus it gets missed. we are scraping every min interval in prometheus

@sushovan23 sushovan23 added the metrics-configuration How to configure specific metrics for collection label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
metrics-configuration How to configure specific metrics for collection
Projects
None yet
Development

No branches or pull requests

1 participant