Go to any graph and show the last 24hrs. Look in the text boxes for setting the graph start/end times. The end time should be the current time (or in your case it maybe be future time).

Check event logs. Check syslogs. Check alert emails and see what timestamps they have.

Michael

On 9 March 2017 1:47:22 PM LHDT, "Ross [Eve IT]" <ross@eve-it.net> wrote:
>Not sure exactly what you mean ?
>What's the best way to get this info ?
>
>
>On Thu, Mar 9, 2017 at 8:34 AM, Adam Armstrong <adama@memetic.org>
>wrote:
>
>> What do the text elements of the UI say? (outside of the javascript).
>>
>> The graphs are drawn by javascript, which also interacts with your
>local
>> timezone (though i developed that code in the USA, on a timezone
>different
>> to the server, which is in germany, so it shouldn't matter)
>>
>> adam.
>>
>> On 08/03/2017 21:26:23, Ross [Eve IT] <ross@eve-it.net> wrote:
>> Thanks Michael, good reference.
>>
>> However I don't think that's my issue.
>> Is there any way I can debug the traffic accounting module to see
>where
>> this timestamp is being set perhaps ?
>>
>> SUMMARY
>>
>> observium bill accounting
>> Last calculated Thursday, 9 March 2017 @ 08:22:34
>>
>> date on machine
>> root@eros:/usr/share/zoneinfo# date
>> Thursday 9 March  08:23:08 AEDT 2017
>>
>> on observium graph, last plot is
>> 09/03/17  21:20
>>
>> The graph seems to be reporting approx 13 hours in the future.
>>
>> On Thu, Mar 9, 2017 at 6:00 AM, Michael <obslist@smarsz.com> wrote:
>>
>>> Maybe you're confused. In Australia, we call c*nts mate and our
>mates
>>> c*nt...
>>>
>>> Here is a good vmware page on clock and ntpd settings for guests.
>>> https://kb.vmware.com/selfservice/microsites/search.do?
>>> language=en_US&cmd=displayKC&externalId=1006427
>>>
>>> Michael
>>>
>>>
>>>
>>> On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong <adama@memetic.org>
>>> wrote:
>>> >It has to be large to keep the c*nt per square mile density the
>same as
>>> >in normal countries...
>>> >
>>> >...
>>> >
>>> >:D
>>> >
>>> >⁣Sent from BlueMail ​
>>> >
>>> >On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net>
>>> >wrote:
>>> >>Thanks for the response,
>>> >>It is virtual, we did actually vmotion a few hosts to this server
>>> >>including
>>> >>the Observium machine.
>>> >>
>>> >>But I've checked the hypervisor, and its clock is good.
>>> >>Also uses NTP, same as the other Hypervisors.
>>> >>
>>> >>Although good point, I've actually been thinking about that exact
>same
>>> >>thing for logging purposes. UTC across the board as we also span a
>few
>>> >>timezones, Australia is large!
>>> >>
>>> >>
>>> >>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com>
>wrote:
>>> >>
>>> >>> It's very odd as there's no timezone of UTC+21.
>>> >>>
>>> >>> Your Observium instance isn't virtual is it?  We've encountered
>>> >>problems
>>> >>> with guests set to obtain their time from the local clock and
>(on
>>> >>ESXi
>>> >>> hypervisors) have a massive time jump when vmotioned to a new
>host
>>> >as
>>> >>they
>>> >>> grab their time from that clock.  Any inconsistencies between
>the
>>> >>> hypervisors will throw your guests clock big time.  All of a
>sudden,
>>> >>your
>>> >>> guest has jumped +10 hours (and ntpd will often wet its pants
>and
>>> >>refuse to
>>> >>> correct such a huge offset)...
>>> >>>
>>> >>> We had a similar problem to above when one hypervisor was set to
>our
>>> >>local
>>> >>> time (+10/11, same as you) when it was supposed to be set to
>UTC.
>>> >In
>>> >>our
>>> >>> case, we run all of our clocks deliberately in UTC to preserve
>>> >>logging
>>> >>> integrity etc (you never get duplicated log times during the
>>> >daylight
>>> >>> savings shift).
>>> >>>
>>> >>> Might not be your issue, but it may help somebody else (and
>worth
>>> >>keeping
>>> >>> in mind)!
>>> >>>
>>> >>> Michael
>>> >>>
>>> >>>
>>> >>>
>>> >>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net>
>wrote:
>>> >>> >
>>> >>> > Looks correct
>>> >>> >
>>> >>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>>> >>> > +--------------------------------+
>>> >>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>>> >>> > +--------------------------------+
>>> >>> > | 11:00:00                       |
>>> >>> > +--------------------------------+
>>> >>> > 1 row in set (0.00 sec)
>>> >>> >
>>> >>> > mysql>
>>> >>> >
>>> >>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>>> >>> > +--------------------+---------------------+
>>> >>> > | @@global.time_zone | @@session.time_zone |
>>> >>> > +--------------------+---------------------+
>>> >>> > | SYSTEM             | SYSTEM              |
>>> >>> > +--------------------+---------------------+
>>> >>> > 1 row in set (0.00 sec)
>>> >>> >
>>> >>> > mysql>
>>> >>> >
>>> >>> > # date
>>> >>> > Wednesday 8 March  20:55:17 AEDT 2017
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz
><schmitz@eseven.de>
>>> >>wrote:
>>> >>> > MySQL Time ?
>>> >>> >
>>> >>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT]
><ross@eve-it.net>:
>>> >>> >
>>> >>> >> Tried all that, still no go.
>>> >>> >>
>>> >>> >> I've set PHP to the right timezone.
>>> >>> >> NTP is set and running on all our servers.
>>> >>> >>
>>> >>> >> Any other ideas ?
>>> >>> >>
>>> >>> >>
>>> >>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
>>> >>> sophanith.chhom@gmail.com> wrote:
>>> >>> >> Try to use single quote? eg:
>>> >>> >>
>>> >>> >> date.timezone = 'Australia/Melbourne'
>>> >>> >>
>>> >>> >> Then restart httpd service
>>> >>> >>
>>> >>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT]
><ross@eve-it.net>
>>> >>wrote:
>>> >>> >> Hi Sam,
>>> >>> >> thanks for responding.
>>> >>> >> however I already have that set correctly.
>>> >>> >>
>>> >>> >> [Date]
>>> >>> >> ; Defines the default timezone used by the date functions
>>> >>> >> ; http://php.net/date.timezone
>>> >>> >> date.timezone = Australia/Melbourne
>>> >>> >>
>>> >>> >> any other ideas ?
>>> >>> >>
>>> >>> >>
>>> >>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
>>> >>> Sam.Hernandez-gill@qvc.com> wrote:
>>> >>> >>
>>> >>> >> I think that’s usually the php.ini timezone setting when the
>>> >>filtered
>>> >>> time doesn’t match, check out what you have set there, and match
>>> >your
>>> >>> system’s timezone and restart apache
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> From: observium [mailto:observium-bounces@observium.org] On
>>> >Behalf
>>> >>Of
>>> >>> Ross [Eve IT]
>>> >>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>>> >>> >> To: observium@observium.org
>>> >>> >> Subject: [Observium] question regarding traffic accounting
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> Hello all,
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> I'm using traffic accounting for multiple interfaces and have
>>> >>noticed a
>>> >>> strange occurrence.
>>> >>> >>
>>> >>> >> The graphs seem to be be producing the wrong time in the
>graphs.
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> See attached;
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> If you notice the top right corner, 2017/03/08 03:15:04
>>> >>> >>
>>> >>> >> It's Tues 7th here 5:15pm.
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> The server clock is synced NTP.
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> Is there something I've missed here ?
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> Observium 17.3.8420 (rolling)
>>> >>> >>
>>> >>> >> Debian Wheezy.
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> Ross.
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> ----------------------------
>>> >>> >> This message (including any attachments) contains
>confidential
>>> >>> information intended for a specific individual and purpose, and
>is
>>> >>> protected by law. If you are not the intended recipient of this
>>> >>e-mail
>>> >>> (even if the e-mail address above is yours), (i) you may not
>use,
>>> >>copy or
>>> >>> retransmit it, (ii) please delete this message and (iii) please
>>> >>notify the
>>> >>> sender immediately. Any disclosure, copying, or distribution of
>this
>>> >>> message or the taking of any action based on it, is strictly
>>> >>prohibited.
>>> >>> >> ----------------------------
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> _______________________________________________
>>> >>> >> observium mailing list
>>> >>> >> observium@observium.org
>>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> _______________________________________________
>>> >>> >> observium mailing list
>>> >>> >> observium@observium.org
>>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> _______________________________________________
>>> >>> >> observium mailing list
>>> >>> >> observium@observium.org
>>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> >>> >>
>>> >>> >>
>>> >>> >> _______________________________________________
>>> >>> >> observium mailing list
>>> >>> >> observium@observium.org
>>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> >>> >
>>> >>> > _______________________________________________
>>> >>> > observium mailing list
>>> >>> > observium@observium.org
>>> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> >>> >
>>> >>> >
>>> >>> > _______________________________________________
>>> >>> > observium mailing list
>>> >>> > observium@observium.org
>>> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> >>>
>>> >>> _______________________________________________
>>> >>> observium mailing list
>>> >>> observium@observium.org
>>> >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> >>>
>>> >>
>>> >>
>>> >>----------------------------------------------------------
>>> --------------
>>> >>
>>> >>_______________________________________________
>>> >>observium mailing list
>>> >>observium@observium.org
>>> >>http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>> _______________________________________________
>>> observium mailing list
>>> observium@observium.org
>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>>
>>
>> _______________________________________________ observium mailing
>list
>> observium@observium.org http://postman.memetic.org/
>> cgi-bin/mailman/listinfo/observium
>>
>>
>> _______________________________________________
>> observium mailing list
>> observium@observium.org
>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>>
>>
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium