1 Title: local: New state type P for state computation based on perfdata
8 The section <tt><<<local>>></tt> now allows a new state
9 marker <tt>P</tt> (next to <tt>0</tt>, <tt>1</tt>, <tt>2</tt> and <tt>3</tt>).
10 When setting this marker, the check plugin computes the state according to the
11 levels contained in the performance data. Take the following example:
15 P Environment temp=30;28;35|humidity=33;40:60;35:70;0;100 This is a text
18 The check will first check the variable <tt>temp</tt>. It's current value
19 is <tt>30</tt>. The levels are at <tt>28</tt> and <tt>35</tt> for warning and
20 critical, resp. Because 30 is greater then 28 this will trigger a warning.
22 The second performance value <tt>humidity</tt> has both lower and upper
23 levels for warning and critical - separated by a colon. The
24 current value is 33, which is lower than the lower critical level
25 of <tt>35</tt>. This will make this variable und thus the total check critical.
30 <li>It is allowed to use fractional values like <tt>35.12</tt>.</li>
31 <li>If the current value exactly matches a level, the <i>better</i> state is being used. This
32 is not consistent with the usual levels in Check_MK checks, but is neccessary if you want
33 to have just one single value to be OK.</li>
34 <li>When using <tt>P</tt> then the current values of all variables are appended to the plugin output.
35 If you want you can omit the your additional text at all in that case.</li>
36 <li>When you use <tt>P</tt> and do not supply performance data or do not supply levels, the
37 status will always be <b>OK</b>.</li>
40 Example for a <tt>local</tt> line without a text:
44 P Environment temp=30;28;35|humidity=33;40:60;35:70;0;100
50 CRIT - temp 30.0 > 28.0(!), humidity 33.0 < 35.0(!!)