Triggering Investigations from GCP Error Reporting

You can wire GCP Error Reporting notifications to a Firetiger agent so that a new investigation starts automatically the moment an error group fires. Error Reporting POSTs the error details — exception type and message, the affected service and version, the request that triggered it, and a link back to the Error Reporting console — and the agent receives all of it as its opening prompt, ready to pull relevant logs and traces from around the time of the error.

This works because every Firetiger agent exposes a stable webhook URL, and GCP can deliver Error Reporting notifications to any webhook endpoint.

Prerequisites

You’ll need the webhook URL for the agent you want to invoke. Open the agent in Firetiger, look at the Triggers section, and copy the Webhook URL. It’ll look like https://api.cloud.firetiger.com/webhooks/dGhpc0lzQVRlc3RUb2tlbjEyMzQ1Njc4OTA. See Agent Webhooks for more detail on how webhook invocation works.

No API key is required — the opaque token in the URL is the credential, so treat the URL as a secret.

Create a webhook notification channel

GCP delivers Error Reporting notifications through a Cloud Monitoring notification channel, so you create the webhook channel there first.

  1. In the Google Cloud console, go to Monitoring → Alerting.
  2. Click Edit notification channels.
  3. In the Webhook section, click Add new.
  4. Paste the Firetiger webhook URL as the Endpoint URL. Leave authentication set to None — the token in the URL is the credential.
  5. Click Test Connection to confirm GCP can reach the endpoint, then Save.

Test Connection fires the trigger. GCP’s Test Connection sends a real POST to the URL, which starts an agent session. That’s expected — you can ignore or delete the resulting test session in the Firetiger UI.

Attach the channel to Error Reporting

  1. Go to the Error Reporting page in the Google Cloud console.
  2. Click Configure notifications.
  3. In the Notification channels drop-down, select the webhook channel you just created.
  4. Click Save.

Error Reporting will now POST to your Firetiger webhook whenever it detects a new error group (or a resolved error reoccurring).

What the agent receives

When a notification fires, GCP sends a JSON body that Firetiger passes through to the agent verbatim, alongside the request headers. The payload includes:

Field Description
subject A short description of the error group
group_info.project_id The GCP project where the error occurred
group_info.detail_link A link to the error group in the Error Reporting console
exception_info.type The exception class or error type
exception_info.message The error message
event_info.service / event_info.version The reporting service and version
event_info.request_method / request_url / response_status The request that triggered the error
event_info.log_message, referrer, user_agent Additional request context

That’s enough for the agent to orient itself and begin correlating the error with logs, traces, and metrics around the time it occurred.

What happens next

When the webhook fires, Firetiger creates a new agent session and the agent starts working immediately on the Error Reporting payload. You can watch the session on the agent’s page in the Firetiger UI, or poll the sessions API to read its output.

  • Agent Webhooks — Full reference for webhook trigger URLs
  • GCP Cloud Monitoring — Give the agent live access to Cloud Monitoring metrics so it can correlate errors with infrastructure signals
This site uses Just the Docs, a documentation theme for Jekyll.