How to use regex for time filter for specific time range every day

volbulbul · February 2, 2022, 1:19pm

I want to montior every day 21:00 to next day 05:00 but it not possible to this with influxdb 1.8
Is it possible to use regex on timefilter replace hours value to that I want ?

melori.arellano · February 18, 2022, 12:07am

@volbulbul the dashboard time range is set using the time controls. For influxDB the $timeFilter global variable is used to represent the dashboard time range.

Can you share more about where you want to monitor? Is this an alert or a dashboard?

If it’s a dashboard, you can create a URL that has the time range specified in the URL:

volbulbul · February 18, 2022, 1:40pm

I am monitoring water consumptions and normally there shouldnt be be consumption at 21:00 to 05:00. If consuptions happens,I want to be alerted. I didnt achive it with ordinary Influxdb queries, Can I do it with help of Grafana ?

melori.arellano · February 18, 2022, 11:32pm

@volbulbul there isn’t currently an easy way to do this, but I found this PR for our legacy alerting system that looks like what you’re looking for. I encourage you to contribute to the discussion.

I shared this PR with our alerting developers that are working on our new alerting framework.

github.com/grafana/grafana

Alerting: added time based restrictions to alert rules

grafana:main ← bblazei:master

opened 03:02PM - 16 Apr 21 UTC

bblazei

+364 -7

anyone else sick of these +1 emails that go on for years and years and years....…?? well i had some extra time this week and felt like giving this a `go` ;) here's what the alert tab looks like with my changes ![grafana_alert_layout](https://user-images.githubusercontent.com/2244826/115044116-31f61200-9ea3-11eb-8f7a-f80405556342.png) features: - db-agnostic as long as regular alerting is supported - panel level time restrictions - condition level time restrictions - restrictions by day and/or time - backward compatible with existing dashboards (hopefully) tried to minimize touch points as i'm pretty sure this entire alerting framework will change sooner than later. actually had a merge conflict even though i pulled a few days ago. it feels like the alerts started as a super simple straightforward query check (1 condition). then as different needs came up, it slowly got augmented which all the other bells and whistles we see today, like thresholds, frequency, emails, dashboards, etc. however, under the covers, there is still a strong dependency to check specific 'conditions'. based on my interaction with it so far, it doesn't really seem like this is a sustainable design moving forward. also see this ticket comment: https://github.com/grafana/grafana/issues/7832#issuecomment-760227291 i really had to shoe-horn the idea of time to the backend evaluators, especially the idea of a 'parent' time for the whole panel. is it the cleanest code i've written? i'm sure there's a much cleaner way to incorporate with the existing AlertEvaluator's, but like i said, there's a lot of churn in these files and i'm trying to balance my time with minimizing touch points. some gotchas: - dashboard must be saved in order for alerting to take place, backend db is what drives the overall framework - timezone is based on server where grafana backend is running -- there is a context level 'starttime' parameter that gets set when the alerting check is kicked off (driven by top-level 'evaluate every' input) -- that time parameter is what drives the alert range time and there is no guarantee when it actually runs, so be careful about super specific time requirements, probably not good enough for 12:00:01 - no hard checks on min [0, 59] or hour [0-23] - on the dashboard, the 'Test Rule' doesn't evaluate the parent time restriction, only the condition level; so triple-check that's correct - did not test this super thoroughly for backwards compatability (did make some effort); the only additional json changes are labeled 'timeEvaluator' so make a new dashboard and look at it's json to get an idea if you run into trouble - no validation stop on parent level parameters so make sure those are accurate when saving, however will log any errors this fork is off of latest master 4/15/21, but i'm thinking this could be backported to whatever version first had an alerting framework. the files in the framework have changed slightly so i don't think the patch will necessarily apply cleanly, however it should be obvious where the changes go. i have a pretty good handle on the alerting framework now, so if you guys want anything else lemme know. unless it's javascript... i battled that render maze long enough today. ps grafana hmu, my fees are reasonable

I noticed this issue as well, asking for something similar for a dashboard time range:

Topic		Replies	Views
Setting timerange over several days in a dashboard Grafana	6	2489	March 26, 2020
Can I disable $timeFilter (time range) in Grafana? Time Series Panel	1	4823	February 16, 2020
Schedule Alerts	2	260	March 26, 2021
How to filter time range inside a day, when we want to see 3 months metrics? Dashboards dashboard	8	1991	July 29, 2022
Time queries in Grafana Grafana	8	4185	March 2, 2022

How to use regex for time filter for specific time range every day

Related topics