Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature request] Better information about why an alert triggered #7035

Closed
bergquist opened this issue Dec 21, 2016 · 0 comments
Closed

[Feature request] Better information about why an alert triggered #7035

bergquist opened this issue Dec 21, 2016 · 0 comments
Labels
area/alerting Grafana Alerting type/feature-request
Milestone
4.2.0

Comments

@bergquist
Copy link
Contributor

There are currently three reason for an alert to trigger. Conditions, Execution error or No data. For executions errors we add extra information inidicating thats is due to an error but there is currently no way to know if its due to the Condition or No data.

This information should be added to

  • Notifications
  • Annotations
  • Alert history
@bergquist bergquist added this to the 4.2.0 milestone Dec 21, 2016
bergquist added a commit that referenced this issue Jan 17, 2017
@bergquist
docs(changelog): note about closing #7035
276916c
danny-allen pushed a commit to danny-allen/grafana that referenced this issue Jan 17, 2017
@bergquist
feat(alerting): shows when no_data triggered alerts
b2819da 
closes grafana#7035
ref grafana#7257
danny-allen pushed a commit to danny-allen/grafana that referenced this issue Jan 17, 2017
@bergquist
docs(changelog): note about closing grafana#7035
b204bd8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/alerting Grafana Alerting type/feature-request
Projects
None yet
Milestone
4.2.0
Development

No branches or pull requests
1 participant
@bergquist