Feature #7008: Implement most urgently-required features of Issue #3982 - messagefacility - Fermilab Redmine

Feature #7008

Feature #3982: Global message logger extensions

Implement most urgently-required features of Issue #3982

Added by Christopher Green about 5 years ago. Updated almost 5 years ago.

Status:

Closed

Priority:

High

Assignee:

Kyle Knoepfel

Target version:

art - 1.12.04

Start date:

09/15/2014

Due date:

10/31/2014

% Done:

100%

Estimated time:

24.00 h

Spent time:

80.00 h

Duration: 47

Description

Implement the syslog destination as a built-in feature, and provide the server-side script.

History

#1 Updated by Christopher Green about 5 years ago

Status changed from New to Accepted
Assignee set to Kyle Knoepfel
Estimated time set to 24.00 h

#2 Updated by Kyle Knoepfel about 5 years ago

% Done changed from 0 to 30

#3 Updated by Kyle Knoepfel about 5 years ago

% Done changed from 30 to 90

#4 Updated by Kyle Knoepfel about 5 years ago

The syslog destination feature has been added to the messagefacility. We have also added a sample configuration file for rsyslogd and a routing script that places the messages in an sqlite3 database. The database file produced creates up to 5 tables:

MessageHeaders: includes header information for all messages

and some optional tables that include a header Id mapping the message to MessageHeaders:

TimeEvent: messages from Timing service
TimeModule: messages from Timing service
MemoryCheck: messages from SimpleMemoryCheck service
UserMessages: all messages not falling into the above tables

The syslog destination is not supported for the messagefacility statistics printout, which currently prints to stdout, stderr, or a user-specified file. For more details, see the wiki information:

https://cdcvs.fnal.gov/redmine/projects/messagefacility/wiki/Syslog_destination_option