You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I filter metrics using metric_relabel_configs in the scrapeConfigs settings, I am not getting the metrics at the scrape time I want.
Send metrics to AWS Prometheus via ADOT (scraping interval: 10 seconds) and range query the metric information every 10 seconds.
I set metric_relabel_configs to ensure that only certain metrics are stored in Prometheus to save on AWS Prometheus costs.
However, when I set metric_relabel_configs in multiple scrape configs, there is an intermittent delay in metric collection.
If I search directly with the current time, the metrics are intermittently not collected when I search, but when I search again after a few seconds with the same time, the metrics are collected well. Therefore, I think the collection is delayed.
If you look at the image below, you can see that metrics are intermittently not collected for a few seconds on the left, and then all metrics are collected.
The metric_relabel_configs condition was present in the config when the metrics were intermittently not collected, and the metric_relabel_configs condition was missing when the metrics were all collected.
(container_cpu_usage_seconds_total metric image)
Is the delay due to slow filtering?
How do I filter metrics by the metric_relabel_configs condition while collecting data every 10 seconds?
I've deployed EKS 1.29, ADOT as helm chart and am using v0.40.0.
Describe the bug
When I filter metrics using
metric_relabel_configs
in the scrapeConfigs settings, I am not getting the metrics at the scrape time I want.Send metrics to AWS Prometheus via ADOT (scraping interval: 10 seconds) and
range query
the metric information every 10 seconds.I set
metric_relabel_configs
to ensure that only certain metrics are stored in Prometheus to save on AWS Prometheus costs.However, when I set
metric_relabel_configs
in multiple scrape configs, there is an intermittent delay in metric collection.If I search directly with the current time, the metrics are intermittently not collected when I search, but when I search again after a few seconds with the same time, the metrics are collected well. Therefore, I think the collection is delayed.
If you look at the image below, you can see that metrics are intermittently not collected for a few seconds on the left, and then all metrics are collected.
The
metric_relabel_configs
condition was present in the config when the metrics were intermittently not collected, and themetric_relabel_configs
condition was missing when the metrics were all collected.(
container_cpu_usage_seconds_total
metric image)Is the delay due to slow filtering?
How do I filter metrics by the
metric_relabel_configs
condition while collecting data every 10 seconds?I've deployed EKS 1.29, ADOT as helm chart and am using v0.40.0.
The text was updated successfully, but these errors were encountered: