10 More Discussions You Might Find Interesting
1. Infrastructure Monitoring
Hello,
I am trying to get correct syntax to monitoring process running on windows server using CheckProcState. when i am trying below command whether notepad.exe running or not. its showing process running.
Could you please provide me correct syantx.
/usr/local/nagios/libexec/check_nrpe -H... (0 Replies)
Discussion started by: ghpradeep
0 Replies
2. Infrastructure Monitoring
Hello All,
I have urgent requirement to monitor Exchange Database (TESTDB) disk space and it is under Disk3 partition. Currently installed NSClient++ in Exchange server. We have Nagios Xi installed in another server. Can you let me know what are configuration files that I need to modify.
... (0 Replies)
Discussion started by: bsivavani
0 Replies
3. AIX
Hi,
is any one using nagios monitoring solution on AIX ? if yes, is it supported on AIX 7.1 TL 03 as well ?
I tried to search online and unix.com , could not find it.
Thank you (5 Replies)
Discussion started by: aaron8667
5 Replies
4. Infrastructure Monitoring
We have a dual Nagios server setup. One is setup for internal server monitoring on our LAN, while the second Nagios server is hosted externally and is used for external checks only such as URL and ping checks form the WAN side.
I was wondering if there is any way to setup cross dependencies... (1 Reply)
Discussion started by: eugenes18t
1 Replies
5. Infrastructure Monitoring
Hello,
What would be the best way to monitor a vmware server through a Draytek firewall using Nagios?
I'm quite new to nagios and any help would be greatly appreciated.
Also I have been trying to monitor my Windows 2003 server using nagios, I am not having much luck. I tried to use this guide:... (2 Replies)
Discussion started by: Jethro
2 Replies
6. Infrastructure Monitoring
Hi all,
I am not being able to monitor CPU of freeBSD machine from my CentOS server. I have used check_aix_cpu but always gives garbage value, seems wrong in scripting. i want to monitor CPU usage of my freeBSD machine from my centOS
server. I am able to monitor many services of that machine... (0 Replies)
Discussion started by: gsuwal
0 Replies
7. Infrastructure Monitoring
Hi, I have configured check_snmp plugin and using the plugin i am able to monitor the uptime of the switch.
But the following fails
# /usr/local/nagios/libexec/check_snmp -H 10.10.10.1 -C ready -o ifOperStatus.1 -r 1 -m RFC1213-MIB
SNMP CRITICAL - *down(2)* |
#
Any suggestions ? (1 Reply)
Discussion started by: uxadmin007
1 Replies
8. Shell Programming and Scripting
*This is not homework I am new to UNIX and want to try this Monitoring a file demo*
*If this is the wrong forum please move it - im new to the forums*
$1 = the file to be monitored
$2 = the time for the file to sleep
If the file gets changed (using -nt) it will send my username mail saying... (2 Replies)
Discussion started by: Nolan-
2 Replies
9. UNIX for Dummies Questions & Answers
Folks;
I have 2 NIC cards on my SUSE Linux server. One of them was reporting receive errors for a while now it's OK, but i'd like to monitor it.
Is there any command i can run to tell me the usage in the past or give me a history of traffic and the speed that going on this specific card?
I... (1 Reply)
Discussion started by: Katkota
1 Replies
10. Infrastructure Monitoring
Nagios is a free, open source enterprise-class network and server monitoring system that can benefit your IT infrastructure. Bill Bradford describes how to install and set up Nagios on a Solaris 10 system. For this example Bill uses Solaris 10 update 6 running in 32-bit mode on a VMware virtual... (0 Replies)
Discussion started by: Linux Bot
0 Replies
COLLECTD-NAGIOS(1) collectd COLLECTD-NAGIOS(1)
NAME
collectd-nagios - Nagios plugin for querying collectd
SYNOPSIS
collectd-nagios -s socket -n value_spec -H hostname [options]
DESCRIPTION
This small program is the glue between collectd and nagios. collectd collects various performance statistics which it provides via the
"unixsock plugin", see collectd-unixsock(5). This program is called by Nagios, connects to the UNIX socket and reads the values from
collectd. It then returns OKAY, WARNING or CRITICAL depending on the values and the ranges provided by Nagios.
ARGUMENTS AND OPTIONS
The following arguments and options are required and understood by collectd-nagios. The order of the arguments generally doesn't matter, as
long as no argument is passed more than once.
-s socket
Path of the UNIX socket opened by collectd's "unixsock plugin".
-n value_spec
The value to read from collectd. The argument is in the form "plugin[-instance]/type[-instance]".
-H hostname
Hostname to query the values for.
-d data_source
Each value_spec may be made of multiple "data sources". With this option you can select one or more data sources. To select multiple
data sources simply specify this option again. If multiple data sources are examined they are handled according to the consolidation
function given with the -g option.
-g none|average|sum
When multiple data sources are selected from a value spec, they can be handled differently depending on this option. The values of the
following meaning:
none
No consolidation if done and the warning and critical regions are applied to each value independently.
average
The warning and critical ranges are applied to the average of all values.
sum The warning and critical ranges are applied to the sum of all values.
percentage
The warning and critical ranges are applied to the ratio (in percent) of the first value and the sum of all values. A warning is
returned if the first value is not defined or if all values sum up to zero.
-c range
-w range
Set the critical (-c) and warning (-w) ranges. These options mostly follow the normal syntax of Nagios plugins. The general format is
"min:max". If a value is smaller than min or bigger than max, a warning or critical status is returned, otherwise the status is
success.
The tilde sign (~) can be used to explicitly specify infinity. If ~ is used as a min value, negative infinity is used. In case of max,
it is interpreted as positive infinity.
If the first character of the range is the at sign (@), the meaning of the range will be inverted. I. e. all values within the range
will yield a warning or critical status, while all values outside the range will result in a success status.
min (and the colon) may be omitted, min is then assumed to be zero. If max (but not the trailing colon) is omitted, max is assumed to
be positive infinity.
-m If this option is given, "Not a Number" (NaN) is treated as critical. By default, the none consolidation reports NaNs as warning. Other
consolidations simply ignore NaN values.
RETURN VALUE
As usual for Nagios plugins, this program writes a short, one line status message to STDOUT and signals success or failure with it's return
value. It exits with a return value of 0 for success, 1 for warning and 2 for critical. If the values are not available or some other error
occurred, it returns 3 for unknown.
SEE ALSO
collectd(1), collectd.conf(5), collectd-unixsock(5), <http://nagios.org/>
AUTHOR
Florian Forster <octo at verplant.org>
5.1.0 2012-04-02 COLLECTD-NAGIOS(1)
