Feat/83 grafana alerts and rules#129
Merged
AllanDantas21 merged 6 commits intomainfrom Mar 21, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds Prometheus alerting rules and an Alertmanager container to support alert evaluation and routing in the existing Grafana/Prometheus monitoring stack.
Changes:
- Configures Prometheus to load rule files and send alerts to Alertmanager.
- Introduces an initial set of Prometheus alert rules (availability, host resources, containers).
- Adds Alertmanager service + persistent volume to docker-compose.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| infra/prometheus/config/prometheus.yml | Enables rule loading and Alertmanager integration in Prometheus config |
| infra/prometheus/config/alerts.yml | Adds initial alert rule groups (availability/resources/containers) |
| infra/docker/docker-compose.yml | Mounts Prometheus config directory and adds Alertmanager service + volume |
| infra/alertmanager/config/alertmanager.yml | Adds baseline Alertmanager routing/receivers configuration |
Comments suppressed due to low confidence (1)
infra/prometheus/config/prometheus.yml:20
- With
--web.route-prefix=/prometheus(see docker-compose), Prometheus serves its own metrics at/prometheus/metrics, but this scrape job uses the default/metricspath. That makes the self-scrape return 404 andup{job="prometheus"}go to 0. Setmetrics_path: /prometheus/metricsfor this job (or drop the route-prefix/external-url approach).
scrape_configs:
- job_name: 'prometheus'
static_configs:
- targets: ['prometheus:9090']
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implementar alertas e regras, fiz tanto no prometheus quanto um container de alertmanager
Internamente está tudo funcionando, mas pelo fato de eu ter adicionado proxy no nginx pro prometheus e mexido na url do prometheus, prometheus não está mais conseguindo se monitorar
Ao tentar retirar a parte de proxy do prometheus, outros exporters (métricas) ficam esquisitos
Obs: podemos otimizar amanhã, por enquanto funciona internamente.. vc consegue observar funcionando em localhost/prometheus/ e entrar na parte de alertas/rules