relating to my last question about SQL-output another idea: the destination-function should have an printf-like option so you can format the output the way you like it; specially for the programm-destination it would be nice to have separators for the different fields to let the program handle and process these during runtime with each message. -- _/ _/ _/ Emil Obermayr QEDEMOB @ EED/E/P _/ _/ _/ fone +49-5121-707-356 fax: -170 _/ _/ _/ http://www.ericsson.de/ecc/fue/standort.html#hildeshm _/ _/ _/ Ericsson Eurolab Deutschland GmbH, Hildesheim, Germany
relating to my last question about SQL-output another idea:
the destination-function should have an printf-like option so you can format the output the way you like it; specially for the programm-destination it would be nice to have separators for the different fields to let the program handle and process these during runtime with each message.
syslog-ng ensures the format of output messages (unlike client syslogds which sometimes omit hostnames, date fields and such) so delimiting the message with spaces should give you the correct results. your feature request has been on my todo list for ages now, but did not have enough time to imlpement it. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
"Balazs" == Balazs Scheidler <bazsi@balabit.hu> writes: >> relating to my last question about SQL-output another idea: >> >> the destination-function should have an printf-like option so you can >> format the output the way you like it; specially for the >> programm-destination it would be nice to have separators for the >> different fields to let the program handle and process these during >> runtime with each message. Balazs> syslog-ng ensures the format of output messages (unlike Balazs> client syslogds which sometimes omit hostnames, date Balazs> fields and such) How do you reliably determine the incoming fields? AFAIK, there is no RFC nor standard for syslog - it is ad hoc. BTW - thanks for the excellent program. j.
Balazs> syslog-ng ensures the format of output messages (unlike Balazs> client syslogds which sometimes omit hostnames, date Balazs> fields and such)
How do you reliably determine the incoming fields? AFAIK, there is no RFC nor standard for syslog - it is ad hoc.
it is ad hoc, just as the parser in syslog-ng is. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
participants (3)
-
Balazs Scheidler
-
Emil Obermayr
-
Jay Soffian