Having a 1 hour gap in data in Spring is one issue, but what about the overlap in Autumn/Fall. Presumably the second hour of metrics overwrites the first hour? That would make for a loss of captured data and consequential regulatory problems.
Corporate systems have only one database and therefore only one "standard time", but with engines scattered world-wide cross monitoring nodes world-wide. Windows platforms are typically defaulted to whatever the local time is at that data centre and polling engines are either in or out of domains & therefore AD's GPO control, but they are polling devices that are often outside their time zone. The only viable solution that I can see is to set the local-time per node, rather than per-engine or per SQL. Obviously we need to correlate it all so it should be based on UTC but using offsets and that way DST can become irrelevant.
Or is that a feature request?