138 Appendix C. Probes• 0 item key =" "1 /0 /item1The remote program will need to output some iteration of the following code to STDOUT:2perldata 32hash 32item key="data" 3 10 2 /item32item key="status_message" 3 status message here 2 /item 32/hash 32/perldata 3The 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 lengthof 1024 bytes. Remote programs that do not include a status_message will still report the valueand 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 changedand it must collect a number as its value.Field ValueCommand*OK Exit Status* 0Warning Exit Status* 1Critical Exit Status* 2Timeout 15Table C-10. General::Remote Program with Data settingsC.4.3. General::SNMP CheckThe 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 returnvalue. It collects the following metric:• Remote Service Latency — The time it takes in seconds for the SNMP server to answer a connectionrequest.Requirements — SNMP must be running on the monitored system to perform this probe. Only integerscan be used for the threshold values.This probe’s transport protocol is User Datagram Protocol (UDP).Field ValueSNMP OID*SNMP Community String* publicSNMP Port* 161SNMP Version* 2Timeout* 15
