[rsyslog] output plugin calling interface
Rainer Gerhards
rgerhards at hq.adiscon.com
Wed May 6 07:18:20 CEST 2009
> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of david at lang.hm
> Sent: Friday, May 01, 2009 10:14 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] output plugin calling interface
> > As a side-note, I have also identified that we have overlooked a subtle
> issue
> > so far: backup actions - they need to work on the subset of the batch
that
> > had message permanent failures. So the message state actually needs to be
> > part of the message inside the batch. But now, I think, things really
begin
> > to come together and are far less complex than initially thought.
> >
> > One problem with the state chart - that was why I said it is not 100%
> correct
> > - is that it does not properly abstract batches vs. single messages. Both
of
> > them entangled in a way that I thought [;)] to be very complex. But if
you
> > model that with processing states, then the batch processing state is
simply
> > a function of the individual message processing states.
> >
> > Please let me know if you also find a math model useful (but I'll
probably
> > need to do it in any case, because it helps me clean up my mind...).
>
> I think it will help clarify things a lot. with a good model we won't have
> misunderstandings about what we are talking about.
I have put on interim version of my model online:
http://www.rsyslog.com/download/design.pdf
Note that it is far from being ready, and some things are not as clear (or
even correct) as I would like to see them. Also, it currently contains
definitions for the various objects, but not any processing information. My
aim is to get a very clear (and dense!) picture of the objects and the
relationships between them from where I am convinced we can find some simple
processing functions (which may or may not be easily enough translated in
code).
Feedback is appreciate, but please keep in mind that the document is a moving
target. I'll be working on it full day today so I hope to have a better
version this afternoon.
Rainer
More information about the rsyslog
mailing list