Date: Tue, 22 Aug 2000 20:57:16 +0200

Actually,

I do exactly that with triggers in the database I send the data =

into.

It is my "gateway to Syslog".

I have very verbose notification/forwarding rules based on =

information

in a different database.

I think a Syslog Daemon should log and transport well, but leave the

parsing of domain specific messages to other domain specific =

applications.

Yes, for this one application, it would be easier to put the

substitution code in Syslog. It must be general. However, if you have a

generic, domain specific parser w/rules; non-Syslog and Syslog =

applications

can use the functionality, much more verbose rule structures can be =

built

and Actions can be tailored to you environment.

I don't know, this is just my opinion.

"Sascha Mettler" <sascha.mettler@bern.ch> wrote in message

news:3A25DBCDF73F2245957BD0B041BEDAF0016554@is1.netal.com...

> Hi everybody

>

> More and more I distribute some of the messages to different people =

which

> have only limited knowledge. E.g. i forward some LAN related Cisco

messages

> to the local IT-Supporter. It would be easier for him to understand a

> message like "TokenRing Tech. Dept. down" than "TokenRing0/0/0 down".

>

> How about a possibility to add some kind of conversion table in a text

file

> to each rule. e.g.

> "TokenRing0/0/0", "TokenRing Tech. Dept."

>

> I know it's possible using external batches with sed or likewise but =

this

> would be a a real pain to manage because all intended actions would =

have

to

> be implemented by hand. Another quite simple approach would be the

> implementation of some kind of preprocessor queue for the service as a

> whole. This would leave some issues open (eg. the fact that a =

conversion

> depends on source) to the preprocessor but it would be much better =

than

> nothing.

>

> What do you think? Anyone could use this too?

>

> greetings from Switzerland

> Sascha

>

>

>