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.

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

Allow setting custom relative time for alert snapshot #6575

Open
calind opened this issue Nov 15, 2016 · 6 comments
Open

Allow setting custom relative time for alert snapshot #6575

calind opened this issue Nov 15, 2016 · 6 comments

Comments

@calind
Copy link

calind commented Nov 15, 2016

Currently alerting snapshot (the image sent by mail) uses the dashboard time (eg. 12 hours ago) or time overrides from Time range graph setting.

It would be useful to have a Time range override per alert rule, so for example in dashboard the graph is displayed for last 12h, but when receiving an alert email the graph is displayed for the last 2h.

@bergquist
Copy link
Contributor

I think both options makes sense. Queries with some aggregations might not show as alerting in the 24h window but in last 2h. I dont think its a good idea to send an image not breaking the threshold.

Perhaps we should send two images?

@calind
Copy link
Author

calind commented Nov 15, 2016

I think one image suffice. What I'm saying is that it would be useful to have a Time range override per alert, which should be taken into account when sending the graph snapshot and computing the thresholds.

This way I can have a zoomed in version in my email, and also for queries doing aggregation (which might be time range sensible) a more stable time range. - All these optional, if I decide I need it.

@arno01
Copy link

arno01 commented Apr 9, 2017

Now that the snapshots are 2h back (the difference between my server set to UTC and my local time), it would also be nice to see an option for specifying the TZ (timezone) for the email alert snapshot.

@maemigh
Copy link

maemigh commented Apr 8, 2021

+1

Copy link
Contributor

This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

@github-actions github-actions bot added the stale Issue with no recent activity label Jan 19, 2024
@armandgrillet
Copy link
Contributor

This request still makes sense with Grafana Alerting but is not a priority in terms of changes for the screenshot service we now use. Removing the label stale and moving this to our backlog.

@armandgrillet armandgrillet removed the stale Issue with no recent activity label Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

6 participants