Create separate RDS instance for Grafana
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Our products are currently reliant on the same Postgres instance used by Grafana. This means that misbehaving products can degrade Grafana's database access and vice versa, making it difficult to debug via logs. We should have separate db instances for Grafana + the products to avoid this.
See the related incident review discussion in Confluence.
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 with the related incident review discussion in Confluence and map how Grafana and the products currently share a Postgres/RDS instance. Define separate Grafana and product database instances, then verify that neither workload can degrade the other's database access; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, grafana, postgresql
- Domain
- cloud, databases, infrastructure, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100