Hi Randy,
In general it is a hard stop at 23:59.00. That is the case if, e.g. you get that number from typing in the time or selecting a time from the dropdown. If, on the other hand, you selected the time by hand (clicking and dragging in the window) then it could include up to 23:59.49. (changing the time by typing in by hand will cause it to go straight to 23:59.00) There are several places where Flows will round to the nearest second, so an occasional millisecond offset should not persist. If you are looking at this level of detail, you should be aware that your exporter might not be accurate to a millisecond level. Hardware exporters often have a little bit of time skew relative to the server running Flows, and sometimes truncate to the second anyway. Software exporters are going to get the time that the packet came to the top of the IP stack, not the time it arrived -- usually a vanishingly small difference, but non-zero. When looking at a single exporter, everything should be consistent, but the time skews may not be the same when examining results from All Exporters on one graph. Regards, Janice Losgar Dartware, LLC (603) 643-9600 x114 On Nov 15, 2010, at 9:27 AM, Randy Baker wrote: > Assume I create a chart in Flows where "Showing data from" is set to start at > "11/13/2010 00:00" and end at "11/13/2010 23:59". > > Does the charting stop at 23:59.00 , or does it include all data between and > 00:59.00 and 00:59.99? > > Randy Baker > Network Security Technician > Georgian College, Barrie, Ontario > Georgian - Recognized as one of Canada's "Greenest Employers" (Earth Day 2010) > > ____________________________________________________________________ > List archives: > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ > To unsubscribe: send email to: [email protected] > ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
