I'm always frustrated when I use hashscan against my app's logs - my app's logs record timestamps in UTC but hashscan displays (for me) PST (which is my local timezone).
(Yes I could adjust it myself. But subtracting 8 mod 12 in my head is hard. I only have 10 fingers, you know.)
Solution
Hashscan should have a configurable setting (by the user) for the timezone he wants to see. Can default to his browser's timezone, which is what it does now (I think).
Problem
I'm always frustrated when I use hashscan against my app's logs - my app's logs record timestamps in UTC but hashscan displays (for me) PST (which is my local timezone).
(Yes I could adjust it myself. But subtracting 8 mod 12 in my head is hard. I only have 10 fingers, you know.)
Solution
Hashscan should have a configurable setting (by the user) for the timezone he wants to see. Can default to his browser's timezone, which is what it does now (I think).
Alternatives
To stop whining and just get on with it.