maddog
(Maddog)
March 3, 2020, 4:32am
1
Dear All
My Watcher can be work & alerted.
but watcher trigger with daily has wrong working.
how to check what wrong of state?
Example Config Watcher Schedule trigger
"trigger": {
"schedule": {
"daily": {
"at": [
{
"hour": [
0,
1,
2,
3,
4
],
"minute": [
0,
5,
10,
15,
20,
25,
30,
35,
40,
45,
50,
55
]
}
]
}
}
}
Result execution history
Hi.
As stated in the documentation: Schedule Trigger | X-Pack for the Elastic Stack [6.2] | Elastic
Schedule triggers define when the watch execution should start based on date and time. All times are specified in UTC time.
so 04:00 UTC + 07:00 timezone offset = 11:00, it is the expected way of working.
I'm afraid there is no easy way to overcome UTC "translations" when working with watcher.
opened 10:15PM - 19 Oct 18 UTC
>enhancement
:Data Management/Watcher
Team:Data Management
**Describe the Feature**:
Since everything runs on UTC scheduled watches do n… ot shift by an hour every time daylight savings time occurs. I have seen since watcher 1.0 was around that it was always considered the responsibility of the user to arrange and maintain scheduled watches regardless of DST changes. For some users this is not easily scalable across multiple clusters with dozens of watches that must occur at the same *relative* time on a daily basis. It would be very useful within watcher to have a designated timezone configuration selection for scheduled watches that must be executed at the same relative time everyday instead of having to manually push the watch forwards or backwards an hour when the time change occurs.
1 Like
maddog
(Maddog)
March 12, 2020, 9:02am
3
Hi Andres
Thank you for the Update.
Now I try to Set schedule time with UTC Time.
My Calculate UTC Time -7 to my settings
IT WORK <3
Thankyou.
system
(system)
Closed
April 9, 2020, 9:02am
4
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.