Mikerowaved wrote:THANK YOU for normalizing the timestamp to my local timezone when viewing the history details. That makes it a whole lot easier than dealing with UTC.
One observation, when hovering over a point in the usage history chart, it gives the date, but all zeros for the hour/min/sec fields.
Yes, the date/time stamps of the Detailed Statistics ("Detailed Logging" screen) are normalized to the user's local time. But date/time on the history graph is UTC time--showing the statistics as of midnight UTC each day. It was troublesome to convert the graph date/time to local time, so the graph date/time remains UTC.
russellhltn wrote:"... [I'm not] sure about the direction of "BW In' and "BW Out". Is that as in "Incoming" (from the Internet) and "Outgoing" (to the Internet)?
"BW In" represents data received FROM the Internet, and "BW Out" means data sent TO the Internet.
Mikerowaved wrote:One observation, when hovering over a point in the usage history chart, it gives the date, but all zeros for the hour/min/sec fields.
Not to mention a 1-week gap from 10/4 to 10/15. Not a big deal, and a non-issue after a couple of months, but something that did give me cause for concern. I didn't think our system was down for that long. <grin>
Prior to the new TM deployment some firewall data was lost. The building networks were not affected (meaning they functioned normally)--just some data was lost. In a few weeks the graph will look normal again.
russellhltn wrote:I noticed the "tag" next to the firewall S/N. "MTG" appears to mean a "Meetinghouse" configuration. "INS" is for "Institute".
The tag next to the firewall serial number indicates the installed firewall configuration. "MTG" = Meetinghouse, "SEM" = Seminary, and "INS" = Institute.
russellhltn wrote:I tried TM on my phone and walked around the stake center to update the labels. A few usability issues.
TM looks best on mobile devices with screen resolution of 1024x768 or better. While the tool is generally usable on smaller screens, it is a better user experience on higher resolution screens (e.g. tablet or PC). TM is not developed as a standalone app (although that would be cool). There is one known limitation for TM running on a mobile device: TM must be used in "public" (not "private") browsing mode.