[Rock-dev] monitoring rock components with rsyslog

[Alexander Duda]

Hi,

at the moment each deployment (process) in rock has one to three log 
files depending on the settings.

* one for the data written to the output ports of the components
* one where all stdout/sdterr mesages of the process are beeing logged
* one for the orocos logger which is by default redirected to stdout/stderr

For all messages written to stdout/stderr we do not have a clear syntax 
and each component has its one style which is pretty bad if something
fails and you have to go through all log files manually. Furthermore the 
log files are stored on the system running the processes therefore if 
something crashes you have to log in to get the log files.

Most of these issues are already addressed by rsyslog and especially the 
CEE enhanced syslog format which is currently under development allowing 
structured messages looks promising. Currently I am looking for a way to 
integrate rsyslog so that all messages to stdout/stderr are 
automatically redirected to a rsyslog daemon running on an other system.

Is someone else interested in this topic or is already using rsyslog 
with orogen components?

Alex

-- 
Dipl.-Ing. Alexander Duda
Unterwasserrobotik

DFKI Bremen
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-456620
Fax:   +49 (0)421 178-454150
E-Mail: alexander.duda at dfki.de

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.:    DE 148646973
Steuernummer:  19/673/0060/3