Closed vmercierfr closed 3 months ago
Package | Line Rate | Health |
---|---|---|
github.com/qonto/prometheus-rds-exporter/internal/app/cloudwatch | 87% | ✔ |
github.com/qonto/prometheus-rds-exporter/internal/app/ec2 | 87% | ✔ |
github.com/qonto/prometheus-rds-exporter/internal/app/exporter | 81% | ✔ |
github.com/qonto/prometheus-rds-exporter/internal/app/rds | 75% | ➖ |
github.com/qonto/prometheus-rds-exporter/internal/app/servicequotas | 51% | ❌ |
github.com/qonto/prometheus-rds-exporter/internal/app/trace | 100% | ✔ |
github.com/qonto/prometheus-rds-exporter/internal/app/unit | 100% | ✔ |
Summary | 80% (1045 / 1305) | ✔ |
Minimum allowed line rate is 60%
Objective
Add instance baseline
Why
Many EC2 instances (e.g. t3 types) have a baseline and max value regarding
IOPS
,throughput
andbandwidth
EBS performances.Since we don't collect baseline information, IOPS/throughput is massively over-evaluated for some instances (e.g. db.t3.small instances)'.
To make it easier to understand for end-user, we named it
burst
in dashboard's panels.In this first iteration, I'm adding throughput information and reflect it in RDS instance dashboard. In a future change, we'll re-avalute how we compute the max disk performance to reflect real Instance performances.
How
rds_instance_baseline_iops_average
andrds_instance_baseline_throughput_bytes
metricsRelease plan