Time stamp in log file needs improvement
The time stamp in the downloaded log file is tough to deal with. First, it appears to be in a unknown time zone. It would be nice to not to have to decode that into the user's time zone. Also, the time is mashed together with the date. Suggestion is to have the time appear in the user's selected time zone, and the date to be in a unique column. Yes, all of this could be handled by the user, but it adds overhead to something that should be direct and simple.
2 replies
-
The timestamp is following the ISO 8601 extended format, and the timezone is always GMT (also known as UTC).
I am assuming you are not programmatically parsing those logs, how are you opening/viewing them?
-
Ah ok on the timestamp standard, I wasn't aware of that. I am not programmatically parsing the logs, I am downloading them and opening in MS Excel and viewing as CSV. I'm looking back a day or so, on a machine that is used for most of a day, which has a large number of DNS queries. Using the web interface is way too cumbersome for that because it only loads so many rows until you have to page down and wait for it to load more rows again. Changing (or adding user friendly timestamps) to the log files would be nice, but perhaps another way to solve my problem would be to add additional filtering options to the existing log file viewer on the web page (and adding sort fields to be used in combination). This would allow me to quickly skip to a date range, filter on one or more domains, etc...
Content aside
- 2 yrs agoLast active
- 2Replies
- 110Views
-
2
Following