Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A class to encapsulate the different log levels accepted by ACS while offering convenient method to create an instance by value or by name, and also a conversion from ACE priorities to ACS log level.

LogThrottle

A utility class to help throttle the publication of log messages. It informs how many log messages can still be sent during the current time interval (Default 1 second). At the end of each interval the log counter is reset to 0.

LogThrottleAlarm

A helper base class for sending alarms associated with not being able to send any more logs in an interval. This class is extended in a specific class to be used by the maciContainer. The reference is passed to the LoggingProxy instance during initialization of the container.

CentralLogger (AcsLogService)

In the LoggingProxy definition this is actually a CORBA Object reference to an object of type AcsLogService. The AcsLogService interface is an extension of the DsLogAdmin::BasicLog interface, which adds two methods:

  • writeRecords: Allows sending a sequence of log messages to the central logger service.
  • getStatistics: Retrieves logging statistics from the central logger service.

The AcsLogService receives the sequence of records and distributes them through the Logging notification channel.

ACE_Log_Msg_Backend

Is the back end processing class from ACE Logger. It can be derived to execute different tasks. For instance in ACS the CacheLogger extends the ACE_Log_Msg_Backend class. These sub-classes are meant to execute the actual work of the logging system.

CacheLogger

It inherits from ACE_Log_Msg_Backend and gives a basic interface for three of its subclasses (LocalFileLogger, LocalSyslogLogger and RemoteSyslogLogger). It includes the following methods:

  • open: It depends on the specific backend, but it can open a file, a network connection, etc.
  • reset: It depends on the specific backend, but it could reset a network connection, etc.
  • close: It depends on the specific backend, but it can close a file, a network connection, etc.
  • log: The specific implementation to log to the desired backend.
  • getIdentification: A backend indentifier name ("Local file", "Local syslog", "Remote syslog", etc.).
  • getDestination: The identifier of the destination depends on the specific backend, but it could be a filename, a single value (i.e. "syslog") or a socket, etc.

LocalFileLogger

LocalSyslogLogger

...