Update status_page_issues usage ping to reflect usages of /publish command
The following discussion from !30906 (merged) should be addressed:
-
@allison.browne started a discussion: (+7 comments) What happens when status page is disabled?
Do we delete the records from
published_incidents
and unpublish?It seems like the check for whether the status page is enabled was removed from the
on_status_page
query.
Relevant Comment from thread:
Summary:
- Snapshot-like data like this isn't actually super helpful for something so transient. A count of currently published issues is a difficult metric to work with, as it does not account for incidents which may have been published & unpublished between the usage ping data being recorded. Disabling status page setting configuration and unpublishing are somewhat tangential to what we want to track.
- We should opt for a counter-like usage ping metric which tracks the number of times the
/publish
command is run, rather than a snapshot of a count of published issues.
I'm going to:
- Open a follow-up MR to transition the
status_page_issues
usage ping metric to a cache-driven action counter, which will only increase over time each time/publish
is used.
Edited by Sarah Yasonik