Since SQL-based data sources can store their timestamps in any time zone offset, it is important for the Visual KPI Server to understand which timezone that data is coming from. Prior to this, Visual KPI assumed time stamps were local to the server but that is not always the case.
As an example, if you are getting data from an ODBC or OLEDB data source (maybe production numbers) and the timestamp for each record is 1:00 PM and that database is in Alaska, but the Visual KPI server is in Arizona, there will be a 2 hour offset in time. Visual KPI recognizes this offset and displays the data properly.
If you have questions about time offsets or anything else, please contact us at firstname.lastname@example.org or call +1/925/218-6983.
Last updated on November 8, 2013 by Transpara