Nagios server Reports

[[email protected]]

I need to pull a long term report (CPU, Memory, I/O, SPACE) on the Nagios server itself. We are looking at splitting our server into multiple Nagiso servers to spread the load. I am not the best Nagios person, in fact I am just the Linux admin. I have access to the dashboard and the report section did not produce. I see the admin section with the real time data but I would like to see that information for a few months. I'll do some more digging and I even plan to RT*M a bit and see if I can figure it out. But if any lose knowledge is floating about on this subject ? ? Thanks

Jim

[tmcdonald]

What problem specifically were you looking to address in this topic?

[[email protected]]

No problem. I need to right size our Nagios configuration to split the monitoring into 4 individual Nagios servers feeding into a Fusion server. I just spoke with your sales team on requesting more information. We did have 22K service queries and we had to downsize down to 11K because the single server was over loaded. We would like to recover those 11K service queries and since we are doing some expansion we decided on 4 servers.

[jdalrymple]

If you're just looking for metrics over time of the server, can you not just look at the service metrics for localhost?

Besides the metrics gathered by Nagios the process, we don't stuff any other metrics into any magic rabbit-holes on your system.

[[email protected]]

Well you caught me. linux admin not skilled in Nagioseese looking to find easy answers to my questions. I did search many areas on the dashboard and searched for localhost but I have not found what your post referenced. But I am presistent and I will endevor to succeed. If you found it it must be there.

[jdalrymple]

Localhost is just the hostname that is being monitored. All Nagios instances by default monitor localhost and you have to specifically go out of your way to disable it.

Both the Nagios Core and NagiosXI interfaces have search features that should help you find localhost - although you may have renamed localhost to the proper hostname of your server, or even the IP, or anything for that matter.

If you have trouble tracking it down let us know and we'll help you with some pointers to dig it up. It's really odd to be "searching around for localhost"