Past day's rsyslog work log:
2008-02-29
- corrected page title in omsnmp doc
- some stage work on rsyslog loader
- changed obj base object's calling interface to use the new obj_if_t
interface structure
- tweaked omgssapi a bit to use our regular calling conventions
- added "debug" command to debug environment settings
- changed the object/interface system to use a new way of calling, giving
up the numerical object ID. This was necessary as we needed more
extensibility for third-party modules (which don't play at all with
the previous fixed object ID). This is stage work for the object loader.
Please note that I needed to change the object (de)serializer, I can't
outrule that I have introduced bugs there.
- corrected invalid function definition
- converted conf.c to an abstract class
2008-03-01
- added class tcps
- added class tcps_sess
2008-03-02
- changed imtcp to use new classes; seems to work; imgssapi currently broken
Subscribe to:
Post Comments (Atom)
simplifying rsyslog JSON generation
With RESTful APIs, like for example ElasticSearch, you need to generate JSON strings. Rsyslog will soon do this in a very easy to use way. ...
-
Did you ever use TCP to transfer syslog reliably? And do you think that makes you immune against message loss? If so, it's time to think...
-
I gave an invited talk on this topic at LinuxTag 2013 in Berlin. I was originally asked to talk about "rsyslog vs. journal", but r...
-
As most of you know, rsyslog permits to pull multiple lines from a text file and combine these into a single message. This is done with the ...
No comments:
Post a Comment