Skip to content

Change cAdvisor rules to use resources.reservation instead of limit

Administrator requested to merge feature/change-usage-metric into main

Created by: pecigonzalo

We currently use resources.limits to measure CPU and Memory to measure resource saturation, which is a good indicator for hitting the absolute limit (burst), but not of the actually reserved and expected utilization.

This changes the recording rules to use resources.reservations instead.

TODO

  • Test this works with docker-compose

Merge request reports