Nagios Support Forum

Firstly, mods, if I have posted this thread in the wrong subforum please move to where it should be.

So we have multiple pages of services flagged with problems, mainly APs and modems etc, and I would like to work from the longest duration flagged towards to shortest. Although I can sort the first page by duration ascending, if I then go on to the second page the sort order is reset and if I then select sort by duration ascending again I am brought back to the first page. Further, if while on the first page I select order by duration ascending and then select limit results to all or say 250, the sort order is also reset. The same happens if I limit the number first and then select sort by duration ascending.

Basically I can sort by duration ascending, but only the first page.

Is there something I, or my colleague who admins Nagios, can do to sort all of the problem services?

dairefagan wrote:Firstly, mods, if I have posted this thread in the wrong subforum please move to where it should be.

Is this actually a problem with Network Analyzer? It almost sounds like you are posting about XI.

Can you provide screenshots of some sort? I am not exactly sure what "the first page" is in this context.

Agreed.

I just spent ten minutes creating all sorts of problems on our fake network to see what shows up in Network Analyzer, and I'm pretty sure you're talking about XI (or at least, Core). Either way, if you can't maintain the sort on page two, I'd say that's a UI bug.

As in OP, I am not sure this is in the right section, maybe the screenshot below can help make sense of this?

You are using Nagios Core. You can see it in your screenshot, the line one up from the one you blanked out that shows who you are logged in as.

Again, I think it will end up being a bug in the UI code.

Thanks.

Is this something the Nagios devs can fix, do I need to report it somewhere, or is this thread enough of a report? I wonder if our admin updates Nagios often...

@tmcdonald will ensure it gets handled appropriately. In the meantime, Nagios Core 4.0.8 is the latest release version. You're running 4.0.4. You may want to upgrade to the latest version just to see if it fixes it. Or at least read the release notes.

eloyd wrote:@tmcdonald will ensure it gets handled appropriately

Hey now, it's not even noon yet and you expect me to do things?

@dairefagan - If you have a GitHub account you can file an issue here: https://github.com/NagiosEnterprises/nagioscore

Or if not, you can use our tracker: http://tracker.nagios.org/

Otherwise I can report the bug, but I will need to reproduce and confirm it first.

Just be glad I'm not asking you to figure out why our fprobe stopped sending NetFlow data conveniently at midnight on May 1 on TWO of our boxes that are configured from the same image as all the rest.

Thanks for the quick support on this.

So I looked through the changelog and I did not see any fixes since 4.0.4 that sounded like they would fix the issue. I created a github account and this bug report, is it okay? I will ask my colleague who admins Nagios to upgrade, but I will wait until the bug is fixed so I do not have to ask him twice. Any idea when the next release is?

https://github.com/NagiosEnterprises/na ... /issues/42