Elasticsearch: Add Timezone Configuration to Watcher

[SpeechlessWick]

Describe the Feature:

Since everything runs on UTC scheduled watches do not 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.

[elasticmachine]

Pinging @elastic/es-core-infra

[vnil1994]

Any updates for this?

[gchiartosini]

Sorry, do you have any updates for this? I feel a little embarrassed to describe this problem to my customer...

[vjt]

Dear Elastic,

we would be grateful if you can consider giving watcher a configuration variable to be able to schedule watches in a timezone defined by the user.

As per our use case, using the configured time zone of the OS on which the ES node runs or (better) an elasticsearch.yml config option would be sufficient, but I believe a solution that would fit all use cases would be the possibility of configuring the time zone at the single watch level.

Thanks again for your consideration and count me in for testing the feature!

[riccup]

Please, Elastic Team, a mechanism to apply a _designated DST-aware timezone_ to Watchers would be highly appreciated.
In a production environment with dozens of watches, the task of manually updating each individual schedule is time-consuming, highly error-prone, and particularly tricky with watches that need firing at specific relative times; it might even be an extra cost to some, as it should be necessarily carried out on the DST-switch week ends.
Thank you for your consideration.

[mcsmik]

Just came across this post, I'm having a real headache with the timezone being stuck on UTC and the clock switch coming up in a couple weeks will mean I need to script changing all my watches to match the new time and it's all cron expressions... I can't believe something as basic as a timezone hasn't been accounted for. Please add this

[assenzav]

Can you kindly let me know when this issue will be fixed? It is very important for my team and my customer!! Thanks in advance

[Zeromika]

It seems like this issue has little to no attention. Any plan to incorporate this soon?