Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
cperf
Current Version
1.0
Last Release Date
2019-11-23
Compatible With
- Nagios 1.x
- Nagios 2.x
- Nagios 3.x
- Nagios 4.x
- Nagios XI
Owner
License
GPL
Hits
4025
Files:
| File | Description |
|---|---|
| cperf.sh | cperf.sh |
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
It can monitor cpu and memory for more complex output with swap analysis and blocked processes, alarming as critical only in cases where paging and locked processes exist.
This script is able to get status of CPU, memory and swap
It can monitor cpu and memory for more complex output with swap analysis and blocked processes, alarming as critical only in cases where paging and locked processes exist.
To use the script you need to specify whether to monitor cpu or memory using the cpu or mem flag, and including the thresholds for warning and critical next.
Example:
server: / #./cperf.sh
Invalid parameter.
Use: # cperf.sh mem V1 V2 or
# cperf.sh cpu V1 V2
V1 = warning percentage value
V2 = critical percentage value
server: / #./cperf.sh mem 85 95
OK - MEMORY usage at 62 % - SWAP usage at 22 %
server: / #./cperf.sh cpu 85 95
OK - CPU usage at 1 % - 3 processes running - 0 processes blocked
The idea is to generate fewer alerts and generate critical alerts only when there is really CPU contention or low memory, thus eliminating peak usage alerts.
It can monitor cpu and memory for more complex output with swap analysis and blocked processes, alarming as critical only in cases where paging and locked processes exist.
To use the script you need to specify whether to monitor cpu or memory using the cpu or mem flag, and including the thresholds for warning and critical next.
Example:
server: / #./cperf.sh
Invalid parameter.
Use: # cperf.sh mem V1 V2 or
# cperf.sh cpu V1 V2
V1 = warning percentage value
V2 = critical percentage value
server: / #./cperf.sh mem 85 95
OK - MEMORY usage at 62 % - SWAP usage at 22 %
server: / #./cperf.sh cpu 85 95
OK - CPU usage at 1 % - 3 processes running - 0 processes blocked
The idea is to generate fewer alerts and generate critical alerts only when there is really CPU contention or low memory, thus eliminating peak usage alerts.
Reviews (0)
Be the first to review this listing!
