mirror of
https://github.com/akvorado/akvorado.git
synced 2025-12-11 22:14:02 +01:00
2b3c463729
The idea is that alloy can also be used for more. For example, we could introduce Loki (with a `docker-compose-loki.yml`) and it would use alloy too. Alloy configuration needs to be split into several parts and both `docker-compose-prometheus.yml` and `docker-compose-loki.yml` would define it but with an additional volume for their specific part of the configuration (using the `extend` mechanism). However, we don't use the bundled Node Exporter, nor the bundled cAdvisor. It is better to have individual components to avoid reduce the amount of code with elevated privileges (both Node Exporter and cAdvisor need specific privileges). Also, we keep Prometheus instead of switching to the full Grafana stack with Mimir as it is a more common setup and this is not a goal to provide something universally scalable. Also, Prometheus is now behind the private endpoint as it is possible to send metrics.
6 lines
95 B
YAML
6 lines
95 B
YAML
---
|
|
global:
|
|
evaluation_interval: 30s
|
|
scrape_configs:
|
|
# none: everything is done from alloy
|