Page 2 of 2

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Mon Jan 30, 2017 2:32 pm
by lmiltchev
Can you create an event that is going to change the state of a host or service (for test purposes) - i.e. submitting a passive check?

Once, you see some state changes in the "State History" report, go back to the birdseye, and check if the right column will populate.

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Mon Jan 30, 2017 3:02 pm
by atuttle
I forced an alert, Birdseye 3.1.1 populated the right column appropriately.
I used the GUI to update Birdseye to 3.2.0 and the column reverted to stating "No State History".
I loaded the Birdseye 3.1.2 zip and the event displayed again.
I went to "reports/State History" and it is blank for today, it does not show the event I forced.
Has there been some change to the web paths that might have something to do with this?

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Mon Jan 30, 2017 4:18 pm
by dwhitfield
I just updated from 3.1.2 to 3.2.1 without issue, so I don't think there's a file path issue.

Can you send us a screenshot of the state history under Reports?

Also, can you show us the output from your console in Chrome? https://developers.google.com/web/tools ... s/console/ Thanks!

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Tue Jan 31, 2017 10:17 am
by atuttle
Birdseye was working properly when I came in today...
The difference was that I was generating a state change every few hours.
I then updated Birdseye to the current release, it worked, then to version 3.2.1 which also works.
--
Again, the only difference between the non-working and working is that I had multiple state changes within 24 hours.

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Tue Jan 31, 2017 10:59 am
by dwhitfield
Can you show us the output from your console in Chrome? https://developers.google.com/web/tools ... s/console/

If there is sensitive info, feel free to PM. If you do PM, please make sure you update this thread after you do.

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Tue Jan 31, 2017 1:20 pm
by atuttle
Console log:
------------------
jquery-1.12.4.min.js?1485383644:4 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery-1.12.4.min.js?1485383644:4
Navigated to https://nagios-t1.xx.edu/nagiosxi/inclu ... rdseye.php
jquery-1.12.4.min.js?1485383644:4 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery-1.12.4.min.js?1485383644:4
ajax @ jquery-1.12.4.min.js?1485383644:4
get_ajax_data @ core.js?1485383644:40
(anonymous) @ views.js?1485383644:2
i @ jquery-1.12.4.min.js?1485383644:2
fireWith @ jquery-1.12.4.min.js?1485383644:2
ready @ jquery-1.12.4.min.js?1485383644:2
K @ jquery-1.12.4.min.js?1485383644:2

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Tue Jan 31, 2017 2:24 pm
by dwhitfield
atuttle wrote: Again, the only difference between the non-working and working is that I had multiple state changes within 24 hours.
Can you clarify this a bit? I took this to mean that a single state change was not getting picked up, but multiples were. However, in discussing it with other techs, they were thinking the issue was resolved. Certainly I see nothing of note in the console output.

If it is resolved, is it ok if we lock the thread?

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Tue Jan 31, 2017 4:25 pm
by atuttle
It appears as if the old Birdseye included a wider time range then the current one so I never had a message that said there was no state data available.
Also version 3.2.1 is an improvement.
This thread is done, sorry for all the noise.

Re: Birdseye 3.2.0 is bad, need to download previous version

Posted: Tue Jan 31, 2017 4:34 pm
by dwhitfield
atuttle wrote: Also version 3.2.1 is an improvement.
Excellent!
atuttle wrote: This thread is done, sorry for all the noise.
No problem at all. That's why we're here!