Birdseye completely throttling cpu

[WillemDH]

Hello,

It seems when the Birdseye view is opened in a browser somewhere, a httpd process is spawned that consumes 100 % cpu. When trying to browse to Nagios XI in another tab of the same browser (Chrome) the page takes a very long time to load. Tried with Firefox and it seems I'm experiencing the same issue there.

Grtz

Willem

[lmiltchev]

Willem,

You had the same issue in January, which was seemingly resolved after a Firefox upgrade...

Seemsthis was solved after a Firefox upgrade. Thread can be closed.

Grtz

WIllem

http://support.nagios.com/forum/viewtop ... 8&start=10

Did the issue reappear? When did it happen? What is the version of the Nagios XI and Birdseye component that you are currently using?

[WillemDH]

Indeed Ludmill, but it appears I'm seeing this now in Chrome and in Firefox. to be honest I'm not using the Birdseye view a lot as it is not able to hide services and hosts that are in downtime or acknowledged resulting in a very red Birdseye view.. I thought I made a feature request for this, but I can't find it. Maybe it was an internal one? So I'm not sure if the issue re-appeared or it has never really gone away. Nagios XI is at R2.7 and Birdseye is at 3.0.2.

Grtz

[lmiltchev]

I thought I made a feature request for this, but I can't find it. Maybe it was an internal one?

You are correct. It is an internal feature request - task ID=5205. It is done. In ver. 3.0.3, you can hide "handled" issues. It will be available in the next major release of XI.

So I'm not sure if the issue re-appeared or it has never really gone away. Nagios XI is at R2.7 and Birdseye is at 3.0.2.

Things don't always work "as expected" in such large environments as yours. I hope we will be getting some feedback from other users with large installs as we are not able to recreate the issue in-house.

[BanditBBS]

I don't use birdseye at all(and it is my favorite view) because of the CPU spike it causes when initially loading it.

[jomann]

Since the Birdseye component was the first XI component I made here, that's probably the reason it hasn't been optimized. I can definitely take a look at it and tweak it to hopefully not require so many calls to the backend data. It does a lot of ajax calls which could probably be more efficient. You can look forward to it in the next major release.

That being said if it's causing you problems when other people are loading it - and you don't want to use it - you could remove the component folder for now and go without it until the new one is released/

[WillemDH]

Ok, I'll wait for the XI update and will update this thread then if I still have issues. Please leave this open for some time. Tx

[lmiltchev]

No problem. We will keep the thread open.