IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

We would want a feature to be implemented, so that by using a custom metric that receives data at X irregular intervals, and no further data is posted in between, alerts get opened when the metric is below the defined threshold, and close automatically whenever new data is pushed to the metric that it is above the defined threshold.

So if we push data to the metric, and it’s below the threshold, an alert is open, and then if we push another data point in 2 days which is below the threshold as well, the alert remains open, and no new alert is created, but if we push once again data which in this case is above the threshold, the alert gets closed.

How this might work:

It could work as:

1. Alerting condition triggers when data point is below(or above depending on the case) the threshold

2. When a new valid data point is posted, it gets evaluated against the threshold and the specified condition

2.a The data point is still violating the condition, and alerts stay open. Loop back to point 2 until the condition to keep the alert open is no longer met

2.b The data point is no longer violating the condition. Alert closes.

If applicable, reasons why alternative solutions are not sufficient:

Using the settings described in this documentation [1] do not suit the case scenario described above.

[1] https://cloud.google.com/monitoring/alerts/concepts-indepth#partial-metric-data

Other information (workarounds you have tried, documentation consulted, etc):

1. Constant push of data to the metric to avoid the condition from entering an “unknown” state (Not feasible)
2. https://cloud.google.com/monitoring/alerts/concepts-indepth#partial-metric-data (Does not suit this case scenario)