Class IncidentReporter

source code

Known Subclasses:

• NonTrailingIncidentReporter

Once an Incident has been declared, I am responsible for making a durable record all relevant log events. I do this by creating a logfile (a pickle of log event dictionaries) and copying everything from the history buffer into it. I can copy a small number of future events into it as well, to record what happens as the application copes with the situtation.

I am responsible for just a single incident.

I am created with a reference to a FoolscapLogger instance, from which I will grab the contents of the history buffer.

When I have closed the incident logfile, I will notify the logger by calling their incident_recorded() method, passing it the local filename of the logfile I created and the triggering event. This can be used to notify remote subscribers about the incident that just occurred.