Or build your own Graylog server and it doesn't have this issue.
Is there any specific reason for using UTC?
Because it never has a daylight saving problem, it's standard and universal, every system uses it identically, and it is the only option that doesn't play favourites with a region.
So......you just add (say 5, for NY) to everything you see?
Or just work in UTC. In modern international business you always have to adjust the time. Nothing is easier than using UTC which is stable, as a base.
How do you get everyone to play along? Server support? Desktop support? Etc..
You make it a company policy. Times are in UTC. It's pretty easy, you can set desktops through GP or similar. Set servers to UTC. Works like magic. Some people might adjust their own stuff, but if they miss things it's purely a failure on their part that they have no excuse for. In fact, the excuse might be worse than missing things (intentionally breaking policy to not know when to show up.)
Wait, wait...so you expect all your users to also adapt to UTC?
Easier than have them not be able to figure out timezones. It's LESS adaptation, rather than more.
P.S.; While the ability to "pivot" from e.g. alert to metrics to log seamlessly from w/in a single UI is indeed attractive, the time series data model of the PLG stack (Prometheus Loki Grafana) does not lend itself well to "The Tail at Scale" problem.
@ajstringham It is very handy! But steep learning curve. I attended a demo conference at the beginning of January up in Orlando. It was very classy and very informational.
They know how to throw a good shin-dig. There is an annual user conference in Las Vegas in October, I think. Analogous to Spice World.