This documents the support classes for ticketing. With ticketing handlers log records are categorized by location and for every emitted log record a count is added. That way you know how often certain messages are triggered, at what times and when the last occurrence was.
Baseclass for ticketing handlers. This can be used to interface ticketing systems that do not necessarily provide an interface that would be compatible with the BackendBase interface.
Returns the unique hash of a record.
A handler that writes log records into a remote database. This database can be connected to from different dispatchers which makes this a nice setup for web applications:
from logbook.ticketing import TicketingHandler handler = TicketingHandler('sqlite:////tmp/myapp-logs.db')
The default backend that is being used when no backend is specified. Unless overriden by a subclass this will be the SQLAlchemyBackend.
alias of SQLAlchemyBackend
Emits a single record and writes it to the database.
Subclasses can override this to tamper with the data dict that is sent to the database as JSON.
Record either a new ticket or a new occurrence for a ticket based on the hash.
Provides an abstract interface to various databases.
Returns the number of tickets.
Deletes a ticket from the database.
Selects occurrences from the database for a ticket.
Return a single ticket with all occurrences.
Selects tickets from the database.
Records a log record as ticket.
Setup the database backend.
Marks a ticket as solved.
Implements a backend that is writing into a database SQLAlchemy can interface.
This backend takes some additional options:
Implements a backend that writes into a MongoDB database.