Message Queue Handler
- class DIRAC.FrameworkSystem.private.standardLogging.Handler.MessageQueueHandler.MessageQueueHandler(queue)¶
MessageQueueHandler is a custom handler from logging. It has no equivalent in the standard logging library because it is linked to DIRAC.
It is useful to send log messages to a destination, like the StreamHandler to a stream, the FileHandler to a file. Here, this handler send log messages to a message queue server.
There is an assumption made that the formatter used is JsonFormatter
Initialization of the MessageQueueHandler.
queue – queue identifier in the configuration. example: “mardirac3.in2p3.fr::Queues::TestQueue”
Acquire the I/O thread lock.
Add the specified filter to this handler.
Tidy up any resources used by the handler.
This version removes the handler from an internal map of handlers, _handlers, which is used for handler lookup by name. Subclasses should ensure that this gets called from overridden close() methods.
Acquire a thread lock for serializing access to the underlying I/O.
Add the record to the message queue.
record – log record object
Determine if a record is loggable by consulting all the filters.
The default is to allow the record to be logged; any filter can veto this and the record is then dropped. Returns a zero value if a record is to be dropped, else non-zero.
Changed in version 3.2: Allow filters to be just callables.
Ensure all logging output has been flushed.
This version does nothing and is intended to be implemented by subclasses.
Format the specified record.
If a formatter is set, use it. Otherwise, use the default formatter for the module.
Conditionally emit the specified logging record.
Emission depends on filters which may have been added to the handler. Wrap the actual emission of the record with acquisition/release of the I/O thread lock. Returns whether the filter passed the record for emission.
Handle errors which occur during an emit() call.
This method should be called from handlers when an exception is encountered during an emit() call. If raiseExceptions is false, exceptions get silently ignored. This is what is mostly wanted for a logging system - most users will not care about errors in the logging system, they are more interested in application errors. You could, however, replace this with a custom handler if you wish. The record which was being processed is passed in to this method.
- property name¶
Release the I/O thread lock.
Remove the specified filter from this handler.
Set the formatter for this handler.
Set the logging level of this handler. level must be an int or a str.