What Monitoring does not support

The metrics, alarms, logs, checks and status page features that Monitoring does not offer.

Last updated 18 November 2026View as Markdown
  • Metrics from inside a machine: memory, filesystem usage of an instance, process counts. Only what the hypervisor sees is recorded.
  • Percentiles, sub-minute resolution and metric math on custom metrics.
  • OTLP over protobuf or gRPC.
  • Deleting a custom series; it is removed 15 months after its last datapoint.
  • Treating missing data as breaching, or any missing-data rule other than "missing".
  • "M of N" alarms: every evaluation period must cross the threshold.
  • Alarms on a combination of metrics, or on anomalies.
  • Alarms on the machine metrics of a whole database or app rather than of one node or machine. An app's own metrics are those of its deployments.
  • Creating an alarm on a custom series, or changing an alarm's rule, in the console.
  • Re-sending a failed webhook.
  • Confirming an alarm's or a check's email addresses before they are mailed.
  • Logs from compute instances you run yourself, and from managed databases, in Monitoring's log search.
  • Choosing which locations a check runs from.
  • TCP, ping, heartbeat and DNS checks; custom request headers or bodies; methods other than GET and HEAD; intervals under a minute.
  • Changing an uptime check's settings in the console.
  • Custom domains, private (password or sign-in) status pages, maintenance windows, Markdown and logos on a status page.
  • Alerts or status updates by SMS.
  • Changing a status page's address or title in the console.
Did this page help you?