Google Cloud Monitoring integration
Bring GCP alerting-policy notifications into HowlOps as incidents, so GCP workloads are covered by the same on-call flow as everything else.
What this brings you
If part of your stack runs on Google Cloud, its alerting policies can notify HowlOps directly, so a GCP-native alert turns into an incident with the same escalation, status page, and history as everything else you monitor. You stop needing to check the Google Cloud Console separately to know something in GCP is unhealthy.
Setup
- In HowlOps, open Integrations in the sidebar (the Integration Hub).
- Under Bring alerts into HowlOps, click the Google Cloud Monitoring source card, then Generate endpoint to get a token-scoped webhook URL.
- In Google Cloud Console, go to Monitoring > Alerting > Edit notification channels > Webhooks, and add a channel with the endpoint from step 2 as its URL.
- Attach that notification channel to the alerting policy (or policies) you want forwarded.
- Trigger a test alert and confirm the incident appears in HowlOps.
An incident state of closed in the GCP payload closes the matching HowlOps incident. GCP's webhook payload does not always include a severity field; when it's absent, HowlOps applies its default (warning).
See also
- Integrations reference for the endpoint format and the full inbound source list.
- Incidents & severities for how an inbound alert becomes an incident.
Was this page helpful?