The check_tungsten_latency command reports warning or critical status information depending on whether the latency across the nodes in the cluster is above a specific level.
Table 9.1. check_tungsten_latency Options
The command outputs information in the following format:
Where DETAIL includes detailed information about the status report, and LEVEL is:
CRITICAL — latency on at least one node is above the specified threshold level for a critical report. The host reporting the high latency will be included in the DETAIL portion:
WARNING — latency on at least one node is above the specified threshold level for a warning report. The host reporting the high latency will be included in the DETAIL portion:
OK — status is OK; the highest reported latency will be included in the output.
OK: All slaves are running normally (max_latency=0.506)
check_tungsten_latency -w 0.1 -c 0.5CRITICAL: host2=0.506s
Performance information can be included in the output to monitor the status. The format for the output is included in the DETAIL block and separates the maximum latency information for each node with a semicolon, and the detail block with a pipe symbol. For example:
check_tungsten_latency -w 1 -c 1 --perfdataOK: All slaves are running normally (max_latency=0.506) | max_latency=0.506;1;1;;
check_tungsten_latency -w 0.2 -c 0.5 --perfdata --perslave-perfdataCRITICAL: host2=0.506s | host1=0.0;0.2;0.5;; host2=0.506;0.2;0.5;;