Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Some time services and host stop responding due to a poor server performance. I mean, if for some reason (could be lot of concurrency services access, a expensive backup execution on the server or whatever that consume tons of server resources) a server performance is very degraded, that could lead that the server isn't capable to establish any "normal network communication" (without trigger whatever standards timeouts defined for such communication).

Knowing host's performance data (cpu, memory, ...) in case of available during that period (host is not down and despite of its performance degradation still allow plugins collect performance data) could be very useful for sysadmin to try to determine what cause the problem, or at least, if the host performance was good and don't interfered at all in the host/service down.

This problem could be solved using remote active (NRPE) or remote passive (NSCA) if such remote solutions could store (buffered) perf data to be send to central Nagios server when host performance or network outage allow it. I read the doc of both solutions and can't find any reference to such buffer mechanism neither what happened in case that NSCA can't reach Nagios server.

Any idea of how solve this lack of info? so useful for forensic analysis.

EDIT:

My questions isn about which tools I can use to debug perf problems or gather perf data to analysis, but is about how collect (using Nagios) host perf data even during a network outage for its posterior analysis (kind of forensic analysis). The idea is integrate such data to Nagios graphers like pnp4nagios and NagiosGrapther. I know that I could install tools like Cacti in each of my host, and have a kind of performance data collection redundancy, but I really want avoid that and try to solve all perf analysis requirements with one tools: Nagios

share|improve this question
1  
I don't think this is possible with how NPRE/NSCA works, Munin or sar can do what you're looking for though. –  TheFiddlerWins Aug 30 '13 at 14:32
    
Any body know what happened when NSCA can't connect to Nagios? It discard the service check result or store it for the next attempt? Or is completely synchronous? Thanks @TheFiddlerWins –  gsc-frank Aug 30 '13 at 14:36
    
ganglia.info –  dmourati Aug 31 '13 at 8:49
add comment

1 Answer 1

I am not sure about Nagios, But If you can login to server you collect the below details, which will help you to narrow down the issue. With the help of below command you can identify who is consuming more of the CPU and memory. Or is the system is in OOM conditions.

top -n 5 -b 
vmstat 1 50 
iostat -x 2 10
ps -aufx 
sar 1 50 
cat /proc/meminfo 
cat /proc/buddyinfo 
share|improve this answer
    
Thanks for your reply @Vin I know that exist tons of tool to debug performance problems, my questions wasn't about which tools I can use, but about how collect host perf data even during a network outage for its posterior analysis (kind of forensic analysis). The idea is integrate such data to Nagios graphers like pnp4nagios and NagiosGrapther. I know that I could install tools like Cacti in each of my host, and have a kind of performance data collection redundancy, but I really want avoid that and try to solve all perf analysis requirements with one tools: Nagios. –  gsc-frank Sep 1 '13 at 1:14
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.