NMS-6686: Initial revision of SnmpMonitor documentation

http://issues.opennms.org/browse/NMS-6686
Not sure if it has the same meaning...

The monitor's behaviour is that, when "match-all" is set to "count", the
monitor makes sure that, out of the tabular object, at least "minimum"
instances and at most "maximum" instances match the criteria.

So, say you are polling the hrProcessTable and want to make sure there are
at least 5 and at most 10 "http" processes running, you'll want to set
"match-all" to "count", "minimum" to 5, "maximum" to 10, "operand" to
"http", and "operator" to "=".

With this explanation, does my sentence make better sense to you?

Cyrille


On Wed, Jul 23, 2014 at 9:42 AM, mvrueden <notifications@github.com> wrote:

> In opennms-doc/guide-admin/src/asciidoc/text/poller/SnmpMonitor.adoc:
>
> > +This monitors has two basic operation modes:
> > +
> > + - Test the response value of one specific _OID_ (scalar object identifier);
> > + - Test multiple values in a whole _table_.
> > +
> > +To decide which mode should be used, the `walk` and `match-all` parameters ares used.
> > +
> > +See the ``Operating mode selection'' and ``Monitor specific parameters for the SnmpMonitor'' tables below for more information about these operation modes.
> > +
> > +.Operating mode selection
> > +[options="header, autowidth"]
> > +|===
> > +| walk | match-all  | Operating mode
> > +.3+^|`true` | `true` | tabular, all values must match
> > +| `false` | tabular, any value must match
> > +| `count` | tabular, between `minimum` and `maximum` values must match
>
> this is a weired sentences.
> Maybe:
> tabular, values between minimum and maxmium must match?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/OpenNMS/opennms/pull/75/files#r15274790>.
>