Feature #7008
Feature #3982: Global message logger extensions
Implement most urgently-required features of Issue #3982
Description
Implement the syslog destination as a built-in feature, and provide the server-side script.
History
#1 Updated by Christopher Green over 6 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 over 6 years ago
- % Done changed from 0 to 30
#3 Updated by Kyle Knoepfel over 6 years ago
- % Done changed from 30 to 90
#4 Updated by Kyle Knoepfel over 6 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 fromTiming
serviceTimeModule
: messages fromTiming
serviceMemoryCheck
: messages fromSimpleMemoryCheck
serviceUserMessages
: 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
#5 Updated by Kyle Knoepfel over 6 years ago
- Status changed from Accepted to Resolved
- % Done changed from 90 to 100
#6 Updated by Christopher Green over 6 years ago
- Target version set to 1.12.04
#7 Updated by Christopher Green about 6 years ago
- Status changed from Resolved to Closed