Anomaly detection : taking daylight saving time into account

Hi,

At present time, anomaly detection doesn’t seem to take daylight saving time into account. The consequence is a time lag between the calculated envelope and the actual metric.

Here’s an example for the past few days :

• time changing occured the 03/31 at 2PM
• day “1” is bank holiday
• day “2” : first working day since time changing, lag between metric and envelope, and therefore alerts are raised
• day “3” : just the same

→ it would be nice to add this parameter in the calculations 🙂

Thank you.