Move reporting_latency into the database as queryable parameter
this will allow:
- faster generation of event pages and responses
- external processes to directly return
reporting_latency
- users to query latency as a parameter
-
reporting_latency
is returned in httpresponses and igwn-alerts
associated documentation has been updated as well. note than upon deployment, there has to be a database migration. and before the event.save()
loop completes, reporting_latency
will just show up as null.