Bug 1614540 - AlertManager alert hyperlink should contain anchor data to direct user to alert they clicked
Summary: AlertManager alert hyperlink should contain anchor data to direct user to ale...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Frederic Branczyk
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-09 21:04 UTC by Justin Pierce
Modified: 2018-08-17 13:17 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-17 13:17:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Justin Pierce 2018-08-09 21:04:44 UTC
Description of problem:
When an external receiver receives an alert from prometheus/am, e.g. slack, the link to the alert looks something like: 
https://alertmanager-main-openshift-monitoring.1b7d.free-stg.openshiftapps.com/#/alerts?receiver=slack

The link does focus the browser on the specific alert that the user clicked.

Version-Release number of selected component (if applicable):
0.14.0

Steps to Reproduce:
1. Configure prometheus to alert a slack channel
2.
3.

Actual results:
The link submitted into the slack channel will send a user back to the alertmanager, but with not focus on the the alert they were interested in. The user will always go to the top of the page.

Expected results:
The link should send the user to the alert manager & focus the browser window on the alert they clicked in slack (potentially briefly highlighting it visually). If the alert is no longer firing, alert manager could briefly display that the alert is no longer available. 

Additional info:
This is a significant usability issue on a cluster with a sizable number of alerts. 

Found related: https://github.com/prometheus/alertmanager/issues/211

Comment 1 Frederic Branczyk 2018-08-17 13:17:13 UTC
This is an internal request for enhancement. I have created a ticket in Jira, therefore I'm closing this here and we will continue tracking it there: https://jira.coreos.com/browse/MON-298


Note You need to log in before you can comment on or make changes to this bug.