Tom,
>
>
> Getting there; recall that my initial problem is one of understanding what it
> is
> the MIB caters for. I had expected the MIB to cater for a pure Sender, in
> order
> to configure it with where to send what, and I am slightly suprised at that
> omission. As ever, it is a question of reaching rough consensus on questions
> like this.
Right. I will reword the answer.
The MIB serves to monitor entities that receive and/or forward syslog messages
e.g. the unix syslog daemon.
Note that the MIB allows us to monitor all the syslog messages even if we do not
monitor senders. [There is nothing in the MIB that prohibits one from monitoring
the senders for syslog messages, but it is better done by monitoring the entity
that receives syslog messages (from multiple entities) and forwards some of
those
messages].
>
> Likewise, grouping is not something I am familiar with, seeing rather a single
> Collector with proprietary features behind it to filter, disseminate etc.
We are focussing on the simple and primary task of monitoring syslog messages
from
syslog entities. The MIB will support several syslog daemons which are probably
using
various transports (UDP{4|6}, TCP{4|6}, on standard and non-standard ports.).
This
situation does arise in practice. I think that the MIB does take care of that
nicely
using the concept of grouping.
One good way to look at the MIB is as a collection of knobs and dials. Then we
can
ask
a. Do we need another knob or another dial
b. Do we need this knob or that dial
>
> Tom Petch
>
Cheers
Glenn
--
+----------------------------------------------------------+
Cyber Solutions Inc. Phone 022-303-4012
6-6-3, Minami Yoshinari Fax 022-303-4015
Aoba-ku, Sendai, Japan 989-3204 e-mail [EMAIL PROTECTED]
+----------------------------------------------------------+
_______________________________________________
Syslog mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/syslog
