Hello,
I've raised the scrape_interval
to 30m
and I've noticed that there's a minimum amount of calls that, no matter the value for scrape_interval
, will be executed.
Is there any theoretical minimum of GetMetricStatistics
and ListMetrics
calls? Could that be configured or is it "hardcoded"?
Context: I'm trying to reduce the Cloudwatch costs as much as possible in dev/staging environments.
Thanks!
Hello,
I've raised the
scrape_interval
to30m
and I've noticed that there's a minimum amount of calls that, no matter the value forscrape_interval
, will be executed.Is there any theoretical minimum of
GetMetricStatistics
andListMetrics
calls? Could that be configured or is it "hardcoded"?
Context: I'm trying to reduce the Cloudwatch costs as much as possible in dev/staging environments.
Thanks!
--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/bb4258f4-56c4-45cd-8d4c-3cec48de0bd0%40googlegroups.com.
ListMetrics
calls and 380/399 GetMetricStatistics
calls every 5 minutes.GetMetricStatistics
(I've tested 5 minute vs 30 minute scrape, and the number of calls is is reduced by 1/3 aprox) but in a way that is not obvious to me.ListMetrics
calls seems unecessarily high...On Thu, 5 Mar 2020 at 19:10, Albert Serrallé Ríos <aserra...@gmail.com> wrote:
Hello,
I've raised the
scrape_interval
to30m
and I've noticed that there's a minimum amount of calls that, no matter the value forscrape_interval
, will be executed.Is there any theoretical minimum of
GetMetricStatistics
andListMetrics
calls? Could that be configured or is it "hardcoded"?You can expect at least one ListMetrics per configured metric, and then one GetMetricStatistics per relevant metric it finds. These should only ever be happening due to a scrape.Brian
--
Context: I'm trying to reduce the Cloudwatch costs as much as possible in dev/staging environments.
Thanks!
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/bb4258f4-56c4-45cd-8d4c-3cec48de0bd0%40googlegroups.com.
I have 11 metrics configured, and my metrics show 100/105ListMetrics
calls and 380/399GetMetricStatistics
calls every 5 minutes.Certainly, the scraping interval affects the number of calls toGetMetricStatistics
(I've tested 5 minute vs 30 minute scrape, and the number of calls is is reduced by 1/3 aprox) but in a way that is not obvious to me.Also, the number ofListMetrics
calls seems unecessarily high...
--
On Thursday, March 5, 2020 at 8:21:44 PM UTC+1, Brian Brazil wrote:On Thu, 5 Mar 2020 at 19:10, Albert Serrallé Ríos <aserra...@gmail.com> wrote:Hello,
I've raised the
scrape_interval
to30m
and I've noticed that there's a minimum amount of calls that, no matter the value forscrape_interval
, will be executed.Is there any theoretical minimum of
GetMetricStatistics
andListMetrics
calls? Could that be configured or is it "hardcoded"?You can expect at least one ListMetrics per configured metric, and then one GetMetricStatistics per relevant metric it finds. These should only ever be happening due to a scrape.Brian--
Context: I'm trying to reduce the Cloudwatch costs as much as possible in dev/staging environments.
Thanks!
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/bb4258f4-56c4-45cd-8d4c-3cec48de0bd0%40googlegroups.com.
--Brian Brazil
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/691ad00d-ea13-4018-919d-053fbc2b4d90%40googlegroups.com.
region: us-east-1metrics:
- aws_namespace: AWS/CloudFront
aws_metric_name: Requests
aws_statistics: [Sum]
aws_dimensions: [DistributionId, Region]
aws_dimensions_select:
Region: [Global]
global:
scrape_interval: 30m
scrape_timeout: 10s
external_labels:
monitor: 'prometheus-local'
account: 'es-newconstruction-pre'
scrape_configs:
- job_name: 'prometheus'
static_configs:
- targets: ['localhost:8080']
- job_name: 'cloudwatch-exporter'
honor_labels: false
metrics_path: '/metrics'
static_configs:
- targets:
- 'localhost:8001'
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/691ad00d-ea13-4018-919d-053fbc2b4d90%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/bd5ef7f3-d5eb-4128-8017-0b27f3a41098%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/bd5ef7f3-d5eb-4128-8017-0b27f3a41098%40googlegroups.com.