Red Hat NETWORK 3.6 -, Справочное руководство

Страница: 150 / 198

138 Appendix C. Probes
•
0
item key =" "
1/0
/item
1
The remote program will need to output some iteration of the following code to
STDOUT
:
2
perldata
3
2
hash
3
2
item key="data"
3
10
2
/item
3
2
item key="status_message"
3
status message here
2
/item
3
2
/hash
3
2
/perldata
3
The required value for
data
is the data point to be inserted in the database for time-series trending.
The
status_message
is optional and can be whatever text string is desired with a maximum length
of 1024 bytes. Remote programs that do not include a
status_message
will still report the value
and status returned.
Requirements — The Red Hat Network Monitoring Daemon (
rhnmd
) must be running on the moni-
tored system to execute this probe. XML is case-sensitive. The
data
item key name cannot be changed
and it must collect a number as its value.
Field Value
Command*
OK Exit Status*
0
Warning Exit Status* 1
Critical Exit Status* 2
Timeout 15
Table C-10. General::Remote Program with Data settings
C.4.3. General::SNMP Check
The General::SNMP Check probe tests your SNMP server by specifying a single object identifier
(OID) in dotted notation (such as
1.3.6.1.2.1.1.1.0
) and a threshold associated with the return
value. It collects the following metric:
•
Remote Service Latency — The time it takes in seconds for the SNMP server to answer a connection
request.
Requirements — SNMP must be running on the monitored system to perform this probe. Only integers
can be used for the threshold values.
This probe’s transport protocol is User Datagram Protocol (UDP).
Field Value
SNMP OID*
SNMP Community String*
public
SNMP Port* 161
SNMP Version* 2
Timeout* 15