Right now, the remote poller code emits events that cause records to be stored in the 'location_specific_status_changes' table. This is not ideal because most of the UI ignores this table and it is not used for availability calculations.

The remote poller code should create normal outages in the outages table in the database and associate them with the monitoringsystems that generated the outage.