This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

iView timing seems mismatched

We are having some issues with the timing corresponding to the same type of time or compensation for the time. If you look at the iView console/shell you get the date and its the current time for the time zone and is correct. If you try to use like the reporting schedule, we have to comp for about 6 hours earlier for it to work at the time we are needing it to. After a restart yesterday now the time for the reports is 4 hours and the data being gathered is being put into the wrong date range (looks to be 12-13 hours off. Any suggestions or ideas on what is causing this?



This thread was automatically locked due to age.
Parents Reply Children
  • Hi,

    there appears to be a bug in the reporting use of time zones and daylight saving adjustments.

    If you review the report generation time within the report you will more than likely find it refers to gmt and offset, not local time.

    Ian

    UPDATE:- just checked my reports and am very confused. On the 17th of Feb 2018 my reports show GMT +10 (should be +11 for daylight savings) and reports generated at 09.18.00. On the 18th Feb 2018 my report show AEDT and reports generated at 01.18.00. Both days the XG software was v17.0.5 MR5