Component Aggregate Charts Raw Data to use Local Time

I guess in this case I would like the feature request to be collect in UTC, store in UTC and only manipulate at the reporting level letting people choose what time they want the reports/data in.  That being said, at the very least having things consistent across the board would be good.

Yes, this appears to be what's occurring.

In other words, Orion is doing data collections in local time and converting it to UTC for the graphs that are stored in UTC.  At least that is what this behavior would suggest.

So, in the chart that uses UTC, we basically jump from 9:00 UTC (UTC -7) to 10:00 UTC (UTC -8) at time change leaving a gap of data, or time stamps with no data.  In the case of the chart that uses local time, it looks like it probably just re-wrote the data for 2:00AM - 3:00AM when the clocks rolled back.  Does that all sound accurate to you?

I now understand why time travel is so difficult!

Since the clock rolls back one hour it would make sense that there are 12 more values for the same hour, since that hour essentially occurred twice. I would not expect a gap in data unless the clock rolled forward an hour, since that hour never actually occurred.