Problem with Birdseye time display

[Fred Kroeger]

Birdseye is displaying the time in the wrong timezone. It is displaying the time in the original timezone before I moved the server to the other side of the country.
I have gone through http://assets.nagios.com/downloads/nagi ... m_Time.pdf
and everything is showing in the correct timezone except for Birdseye. Is there another setting for this?

Fred

[tmcdonald]

What do you have under Admin -> Manage System Config for your Timezone? That will need to match what you have for the other settings.

[Fred Kroeger]

The timezone in Manage System Config matches the setting in /etc/localtime & /etc/php.ini.

As mentioned, it's *only* the Birdseye screen that shows the time in the previous time-zone.

[Box293]

Give you give us some screenshots showing the time you see in Birdseye vs the time you see under Admin > System Config > System Profile

[Fred Kroeger]

Hi Troy
Screenshots attached - taken within a few seconds of each other.
The Birdseye time is the current WA Time (where VM was originally built) and the System Time is East Coast time.
All other times displayed in Nagios are correct.

regards Fred

[Box293]

OK so I've been looking at the code and the clock is generated through JavaScript. So this means the values for the clock are going to be taken from the workstation displaying this page.

Can you please confirm this is the case with you (your workstation is on WA time)?

[Fred Kroeger]

Yes my desktop is in WA

Happy Melbourne Cup Day!

[Box293]

No public holiday for me, I'm 70km North of the Victorian border lol.

So does this answer your question, or do you have a suggestion / feature request?

[Fred Kroeger]

Thanks Troy
I guess that as long as my East Coast users are seing the correct time on their display then it's OK. Just a bit confusing as all the other screens show the system time.
There is something else though..... the word wrap for the hostname in the Birdseye screen is set too long. Only about 20 chars fits across the box. I think it may be because the hostname is in a larger font than the service details. If I have a hostname with 30+ chars, then it wraps OK.

regards... fred

[Box293]

Can you show us a screenshot demonstrating that behaviour please