thoughtbot / thoughtbot/flightdeck
Label Prometheus metrics by Flightdeck instance
Open
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 100
- Forks
- 11
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 3
Description
When we perform blue/green upgrades to infrastructure, metrics are sent twice: once from the blue cluster, and once from the green cluster. This results in odd artifacts in Grafana as the metrics aren't aggregated correctly. If we add labels like cluster=myapp-production-v2 we can filter by cluster in Grafana.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the Terraform or Kubernetes configuration that emits Prometheus metrics, then review how Grafana consumes them. Done means metrics from blue and green Flightdeck instances carry a distinct cluster label so they can be filtered and aggregated correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, kubernetes, prometheus, terraform
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100