thoughtbot / thoughtbot/flightdeck
High Availability Prometheus toggle for staging envs
Open
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 100
- Forks
- 11
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 3
Description
We're currently running two flightdeck-prometheus nodes for high availability, this isn't necessary on staging or other non-production environments.
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
Start by locating the Terraform module or environment configuration that creates the flightdeck-prometheus nodes, then inspect how staging and other non-production environments are selected. Identify the current high-availability setting and determine how it can be toggled off outside production. Done means non-production plans use one node while production retains two.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus, terraform
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100