NMS-6686: Initial revision of SnmpMonitor documentation

http://issues.opennms.org/browse/NMS-6686
Hello,

I've implemented most of your suggestions.

For the remaining suggestions that I haven't implemented, I've either
forgot them, or I'm not sure it's good to implement them.

Could you please review my updated PR and summarizes the suggestions you
would like to be implemented?

Cyr


On Wed, Jul 23, 2014 at 10:00 AM, Cyrille Bollu <cyrille.bollu@gmail.com>
wrote:

> Yes, the way operation mode of the SnmpMonitor are selected is not
> intuitive at all.
>
> I've filled an enhancement bug for this:
> https://github.com/OpenNMS/opennms/pull/75
>
>
> On Wed, Jul 23, 2014 at 9:58 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
>>
>> After I read the whole document it now makes sense to me ;)
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/OpenNMS/opennms/pull/75/files#r15275271>.
>>
>
>