When an alert fires, it is a bit painful to track down the underlying bq exporter query that generated the metric that the alert is based on.
It would be some work, but each time we respond to an alert, we could create a project saved query, in mlab-oti, named for the metric in the alert, and containing the query that produces the metric. Over time, we would accumulate these queries, which could then be referenced upon future alerts.
For example:
https://console.cloud.google.com/bigquery?sq=240028626237:902ff21050554bb3853c0d0eb86207b1
When an alert fires, it is a bit painful to track down the underlying bq exporter query that generated the metric that the alert is based on.
It would be some work, but each time we respond to an alert, we could create a project saved query, in mlab-oti, named for the metric in the alert, and containing the query that produces the metric. Over time, we would accumulate these queries, which could then be referenced upon future alerts.
For example:
https://console.cloud.google.com/bigquery?sq=240028626237:902ff21050554bb3853c0d0eb86207b1