Provide dashboard without concurrent access limit
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
At the moment our dashboard is directly backed by BigQuery. However, BigQuery has a limit on the number of "interactive" queries set to 100 by default, and increasing it involves negotiating with Google staff, which likely means it won't go much further. This means we can't really offer this dashboard to the general public, as the required queries will quickly exceed the limit.
Find a way to provide interactive access to our dashboard somehow, so it can handle many more users.
Perhaps add another database, like PostgreSQL, serving as a storage for X months of latest data and use that instead for dashboard.
Contributor guide
No contributing guide indexed for this repository
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 kcidb-grafana dashboard and its current BigQuery-backed access. Investigate an approach that avoids BigQuery's interactive-query limit, including the suggested PostgreSQL storage for recent data. Done means the dashboard can provide interactive access to many more users without relying directly on the constrained query path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, postgresql
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100