Alert Webhook

Documentation Index

Fetch the complete documentation index at: https://docs.foggyhq.com/llms.txt

Use this file to discover all available pages before exploring further.

​

What you get

• One endpoint per workspace, authenticated by a Bearer token.
• Every incoming alert is matched against your automation filter rules. Matches kick off an investigation. Non-matches are recorded but ignored.
• Payloads up to 1 MB are accepted. Larger = 413.
• Multiple tokens per workspace (you can rotate or revoke individually).

​

Setup

1. In the Console sidebar, click Integrations.
2. On the Alert Webhook card, click Configure.
3. Click Generate token. Copy the full foggy_wh_... token — it is shown once.
4. Copy the webhook URL (shape: https://<your-foggy-host>/api/v1/projects/<id>/webhooks/alerts).
5. In your alerting tool, add a webhook / HTTP receiver pointing at that URL, with header:
   Authorization: Bearer <token>
   Content-Type: application/json
   
6. Fire a test alert. The webhook returns 200 OK immediately; the investigation runs in the background.

​

Example receiver configs

receivers:
  - name: foggy
    webhook_configs:
      - url: https://foggy.your-company.com/api/v1/projects/1/webhooks/alerts
        http_config:
          authorization:
            type: Bearer
            credentials: <token>

​

Response codes

​

Troubleshooting

• No investigation fires even though the webhook returned 200 — no automation’s filter rules matched the payload. Open any automation, check the filter rules against the alert’s labels.
• 401 on every call — the token was disabled in the UI, or copied wrong. Regenerate in Integrations → Alert Webhook and update your alerting tool’s config.
• 413 on large Alertmanager groups — Alertmanager can batch many alerts into one POST. Set group_wait, group_interval, and repeat_interval in your route to keep payloads under 1 MB.

​

Next steps