prometheus / prometheus/alertmanager
Source links do not work when on same domain as Alertmanager
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
What did you do?
We have prometheus and alertmanager behind a proxy under /alerts and /prometheus. When an alert fires the "Source" element is set to the url domain.com/prometheus?somequery. It seems that the javascript is intercepting this click before the link is resolved.
What did you expect to see?
Link to the proper prometheus page linked in the
What did you see instead? Under which circumstances?
It seems that the javascript is intercepting this click before the link is resolved, because the page quickly shows a "loading" then back to where it was before. If i edit the DOM and make the domain different from alertmanager the link works.
Environment
Kubernetes, prometheus operator helm chart
- System information:
Chrome Version 73.0.3683.103 (Official Build) (64-bit)
- Alertmanager version:
quay.io/prometheus/alertmanager:v0.16.1
- Prometheus version:
quay.io/prometheus/prometheus:v2.7.1
-
Alertmanager configuration file:
n/a frontend issue -
Prometheus configuration file:
n/a frontend issue -
Logs:
n/a
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
No source file or test is named. Start by reproducing the Source-link behavior with Prometheus and Alertmanager on the same domain, then trace the frontend click handling. Done means the Source link opens the proper Prometheus page instead of briefly showing a loading state and returning to the current page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, prometheus
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100