feat(dashboard): per-repo and per-org cost budgets with spend alerts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- analytics, full-stack
Research direction
Start by reading the existing cost persistence and analytics paths and the dashboard entry points; the issue does not name specific files or tests. Map how costs are stored and shown before scoping monthly budgets per repository and organization, configurable spend thresholds, and an in-UI alert. Done when both budget scopes and threshold alerts work in the dashboard; webhook or email alerts are optional.
Written by the indexing model from the issue text.
Description
Problem Statement
The cost/token dashboard is a distinctive feature, but it is reporting-only. Self-hosters who pay their own API bills have no way to set a budget or get alerted when spend approaches it.
Proposed Solution
Add per-repo and per-org monthly cost budgets in the dashboard, with a visual indicator and an alert (in-UI, and optionally webhook/email) when spend crosses configurable thresholds. Builds on the existing cost persistence and analytics.
Alternatives Considered
- External monitoring on the OTel cost counter — possible, but a built-in budget view fits the dashboard.
Priority
Important
Code of Conduct
- I have searched for existing issues and this is not a duplicate.
- Dominant language
- Java
- Stars
- 35
- Forks
- 7
- Avg merge
- 9h 37m
- Merged PRs (30d)
- 148
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from devops-thiago/ThrillhouseBot
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
devops-thiago/ThrillhouseBot#1132 ·
Maintainers usually reply within 1 day
-
fix(review): always name the linked issue and its unmet criterion in the summaryPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#1093 ·
Maintainers usually reply within 1 day
-
documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
devops-thiago/ThrillhouseBot#321 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#46 ·
Maintainers usually reply within 1 day
-
fix(dashboard): login page returns 500 in mock mode (window is not defined)Possibly taken @devops-thiago claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
devops-thiago/ThrillhouseBot#1128 ·
Maintainers usually reply within 1 day
All issues in devops-thiago/ThrillhouseBot
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
refinedmods/refinedstorage2#1421 ·
-
StepExamBenchmarkTest runs a loop and prints a timing but asserts nothingPossibly taken A pull request linked to this issue is open or already merged. Openjules
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-learning-exchange/myplanet#18199 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Scheme-less stream URLs throw NullPointerException instead of URISyntaxExceptionPossibly taken @blihio claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pedroSG94/RootEncoder#2218 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/rocketmq-dashboard#6872 ·
Maintainers usually reply within 3 days