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]: AWS/Connect metrics not appearing in Grafana #654

Open
meridius01 opened this issue Feb 13, 2024 · 1 comment
Open

[metrics]: AWS/Connect metrics not appearing in Grafana #654

meridius01 opened this issue Feb 13, 2024 · 1 comment
Labels
metrics-configuration How to configure specific metrics for collection

Comments

@meridius01
Copy link

Context information

Exporter configuration
  - aws_metric_name: ConcurrentCalls
    aws_dimensions: [InstanceId]
    aws_namespace: AWS/Connect
    aws_statistics: [Average]
Exporter logs

What do you expect to happen?

I just want to have at least ConcurrentCalls to appear on Grafana for monitoring

What happened instead?

The problem is that even I have the right format and settings (including the right IAM role with right permission and trust relationship), I can't see the specific metric of concern in Grafana when Cloudwatch Export was running.

@meridius01 meridius01 added the metrics-configuration How to configure specific metrics for collection label Feb 13, 2024
@matthiasr
Copy link
Contributor

Can you see the metrics in the Prometheus console? In the /metrics endpoint of the exporter? If they show up in the latter, but not in Grafana or the table view in Prometheus, you may be running into this expected behavior.

Thankfully, for this service, AWS actually does specify that data is sent every minute, so you may try delay_seconds: 60 or delay_seconds: 120 which would then work with Prometheus' default lookback.

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

2 participants