Consider having a built-in adapter for Prometheus
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- php, prometheus
- Domain
- observability
Research direction
Start with the Prometheus Alertmanager webhook configuration linked in the issue and review how Cachet components and incidents are represented through its API. Done would require a defined built-in adapter that maps Alertmanager entities to components and resolves incidents when alerts stop firing.
Written by the indexing model from the issue text.
Description
While Cachet currently only concerns itself with displaying statuses (and maintenance messages) for components, these are still to be created/updated manually via the Dashboard (or API). Of course there is the possibility of integrating with Oh Dear, but in the interest of presenting a truly open-source solution that kinda 'closes the loop' it'd be great to have a built-in integration with Prometheus.
At least in the past with v2, there was reasonable demand for such a solution, as elicited by the following 3rd party adapters (which unfortunately are not maintained anymore, and probably don't play well with v3):
As far as I can see, this mostly revolves around having a translator for the webhook events from Prometheus Alertmanager, some way to map the individual entities to components, and of course resolving incidents when they stop firing.
Looking forward to further discussions on this matter!
- Dominant language
- PHP
- Stars
- 228
- Forks
- 84
- Avg merge
- 11h 19m
- Merged PRs (30d)
- 22
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.
More from cachethq/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Banner image upload fails with "The banner image field contains a file path that is not permitted" Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
filament
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
coollabsio/coolify#11927 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100