anchor.diff:                        Note: Comparison will always succeed if either the `operand` or `operator` parameter isn't set
                               and the monitored value is non-null.                                                       | optional | `-`
   | `operator`        | The operator to be used for comparing the monitored object against the `operand` parameter.
  -                      Must be one of the following symbolic operators:
  -                      `<` Less than. Both operand and observed object value must be numeric.
  -                      `>`  Greater than. Both operand and observed object value must be numeric.
  -                      `<=` Less than or equal to. Both operand and observed object value must be numeric.
  -                      `>=` Greater than or equal to. Both operand and observed object value must be numeric.
  -                      `=`  Equal to. Applied in numeric context if both operand and observed object value are numeric,
  -                           otherwise in string context as a case-sensitive exact match.
  -                      `!=` Not equal to. Applied in numeric context if both operand and observed object value
  -                           are numeric, otherwise in string context as a case-sensitive exact match.
  -                      `~`  Regular expression match. Always applied in string context.
  +                      Must be one of the following symbolic operators: +
  +                      `&lt;` (<): Less than. Both operand and observed object value must be numeric. +
  +                      `&gt;` (>): Greater than. Both operand and observed object value must be numeric. +
  +                      `&lt;=` (<=): Less than or equal to. Both operand and observed object value must be numeric. +
  +                      `&gt;=` (>=): Greater than or equal to. Both operand and observed object value must be numeric. +
  +                      `=`: Equal to. Applied in numeric context if both operand and observed object value are numeric,
  +                           otherwise in string context as a case-sensitive exact match. +
  +                      `!=`: Not equal to. Applied in numeric context if both operand and observed object value are
  +                            numeric, otherwise in string context as a case-sensitive exact match. +
  +                      `~`:  Regular expression match. Always applied in string context. +
                         Note: Comparison will always succeed if either the `operand` or `operator` parameter isn't set
                               and the monitored value is non-null.
                         Keep in mind that you need to escape all < and > characters as XML entities (`&lt;` and `&gt;`
  -                      respectively) if you are editing the `poller-configuration.xml` file by hand.                      | optional | `-`
  -| `port`            | Destination port where the SNMP requests shall be sent.                                          | optional | `from snmp-config.xml'
  +                      respectively)                                                                                    | optional | `-`
  +| `port`            | Destination port where the SNMP requests shall be sent.                                          | optional | from 'snmp-config.xml'
   | `reason-template` | A user-provided template used for the monitor's reason code if the service is unvailable.
                         Defaults to a reasonable value if unset.
  -                      See below for an explanation of the possible template parameters.                                 | optional | 'depends on operation mode'
  -
  -| `retry`           | Number of polls to attempt.                                                                      | optional | `from snmp-config.xml`
  -| `retries`         | Deprecated.
  -                      Same as `retry`.
  -                      Parameter `retry` takes precedence if both are set.                                              | optional | `from snmp-config.xml`
  -| `timeout`         | Timeout in milliseconds for retrieving the object's value.                                       | optional | `from snmp-config.xml`
  -| `walk`            | If set to `false`, sets the monitor to poll for a scalar object unless if the `match-all` 
  -                      parameter is set to `count`, in which case the `match-all` parameter takes precedence.
  -                      If set to `true`, sets the monitor to poll for a tabular object where the `match-all` parameter
  -                      defines how the tabular object's values must match the criteria defined by the `operator` and
  -                      `operand` parameters.
  -                      See also the `match-all`, `minimum`, and `maximum` parameters.                                   | optional | `false`
  +                      See below for an explanation of the possible template parameters.                                | optional | depends on operation mode
  +
  +| `retry`           | Number of polls to attempt.                                                                      | optional | from 'snmp-config.xml'
  +| `retries`         | *Deprecated* Same as `retry`. Parameter `retry` takes precedence if both are set.              | optional | from 'snmp-config.xml'
  +| `timeout`         | Timeout in milliseconds for retrieving the object's value.                                       | optional | from 'snmp-config.xml'
  +| `walk`            | `false`: Sets the monitor to poll for a scalar object unless if the `match-all` parameter is set
  +                      to `count`, in which case the `match-all` parameter takes precedence. +
  +                      `true`: Sets the monitor to poll for a tabular object where the `match-all` parameter defines how
  +                      the tabular object's values must match the criteria defined by the `operator` and `operand`
  +                      parameters. See also the `match-all`, `minimum`, and `maximum` parameters.                       | optional | `false`
   |===
   
   .Variables which can be used in the reason-template parameter
  
positive.code:  should be replaced.
  ----
  
  .Example SnmpMonitor as HP Insight physical drive monitor in poller-configuration.xml
  [source, xml]
  ----
  
negative.code: <1> OID for SNMP table with all physical drive states
  <2> Enable _walk mode_ to test every entry in the table against the test criteria
  <3> Test operator for integer
  <4> Integer `2` as operand for the test
  <5> Test in _walk mode_ has to be passed for every entry in the table
  <6> Encode _MIB_ status in the reason code to give more detailed information if the service goes down
  
  ==== Example test SNMP table with all matching values
  
  This example shows how to use the SnmpMonitor to test if the number of static routes are within a given boundary.
  The service is marked as _up_ if at least 3 and at maxium 10 static routes are set on a network device.
  This status can be monitored by polling the table _ipRouteProto_ from the http://www.ietf.org/rfc/rfc1213.txt[RFC1213-MIB2].
  
   ipRouteProto 1.3.6.1.2.1.4.21.1.9
  
  The _MIB_ description gives us the following information:
  
  [source, asn1]
  ----
  