Class RILogPublisher

Return a dict that maps an 'incident name' (a string of the form 'incident-TIMESTAMP-UNIQUE') to the triggering event (a single event dictionary). The incident name can be passed to get_incident() to obtain the list of events (including header) contained inside the incident report. Incident names will sort in chronological order.

If the optional since= argument is provided, then this will only return incident names that are alphabetically greater (and thus chronologically later) than the given string. This can be used to poll an application for incidents that have occurred since a previous query. For real-time reporting, use subscribe_to_incidents() instead.

Subscribe to hear about new Incidents, optionally catching up on old ones.

Each new Incident will be reported by name+trigger to the observer by a new_incident() message. This message will be sent after the incident reporter has finished working (usually a few seconds after the triggering event).

If catch_up=True, then old Incidents will be sent to the observer before any new ones are reported. When the publisher has finished sending the names of all old events, it will send a done_with_incident_catchup() message to the observer. Only old Incidents with a name that is alphabetically greater (and thus later) than the since= argument will be sent. Use since='' to catch up on all old Incidents.

Call unsubscribe() on the returned RISubscription object to stop receiving messages.

__bases__

Value:

(<RemoteInterfaceClass foolscap.remoteinterface.RemoteInterface>)

__iro__

Value:

(<RemoteInterfaceClass foolscap.logging.interfaces.RILogPublisher>, <RemoteInterfaceClass foolscap.remoteinterface.RemoteInterface>, <InterfaceClass zope.interface.Interface>)

__sro__

Value:

(<RemoteInterfaceClass foolscap.logging.interfaces.RILogPublisher>, <RemoteInterfaceClass foolscap.remoteinterface.RemoteInterface>, <InterfaceClass zope.interface.Interface>)