Central Federated/Aggregated Gardener Monitoring Dashboards #5
Labels
area/monitoring
Monitoring (including availability monitoring and alerting) related
kind/enhancement
Enhancement, improvement, extension
kind/roadmap
Roadmap BLI
lifecycle/icebox
Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.)
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
status/accepted
Issue was accepted as something we need to work on
topology/garden
Affects Garden clusters
We would like to have a federated/aggregated Gardener monitoring spanning all infrastructures, seeds, and shoots. The idea was to either use Thanos (disadvantage 2h skew) or Cortex (disadvantage separate Cassandra DB) to federate/aggregate the data (also behind firewalls) and preserve the data thereby for longer (e.g. average CPU and memory utilisation per cluster in shoot Prometheus/all clusters with reduced granularity/metrics in central Prometheus).
The text was updated successfully, but these errors were encountered: