Skip to main content

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.

Automations run investigations automatically — either on a schedule or when alerts fire — and deliver results to the web interface and Slack.

How it works

1

Trigger

An automation runs on its schedule (e.g. 09:00 every morning) or when an alert matches its filter rules.
2

Investigate

Foggy runs the investigation using your connected data sources — querying metrics, logs, dashboards, and cluster state, just like a manual investigation.
3

Deliver

Results appear as a chat thread in the web interface and are delivered to Slack (if configured). Full chain-of-thought, sources, and follow-up suggestions included.

Alert-triggered automations

Configure automations that fire when alerts come in. Define filter rules to control which alerts trigger investigations.

Filter rules

Filter rules match against alert labels. Multiple rules use AND logic — all must match for the automation to trigger. Common patterns:
PatternFilter rulesUse case
Critical onlyseverity = criticalInvestigate only high-impact alerts
Service-scopedseverity = critical + service = checkoutFocus on a specific service
Namespacenamespace = productionIgnore staging/dev alerts
Broad triagealertname = HighErrorRateAuto-investigate a specific alert type
Start narrow (e.g. severity = critical for one service) and expand as you build confidence.
Alert trigger configuration

Run now

Every automation — scheduled or alert-triggered — has a Run now button on its detail page. This executes the automation immediately against live data, independent of its schedule or filter rules. Useful for testing a new automation, or to re-run one after fixing a connector.

Scheduled automations

Set up investigations that run on a recurring schedule — no alerts required.
FrequencyConfiguration
DailyRuns every day at selected times
WeeklySelect specific days (e.g. Mon, Wed, Fri) and times
MonthlySelect specific days of the month (1–31) and times
One-timePick a specific date and time for a single run
All frequencies support multi-select times — e.g. run at both 09:00 and 17:00. Schedule configuration modal

Next steps

Slack Bot

Investigate incidents and get automation results directly in Slack.

Knowledge Base

Add runbooks and context so Foggy gives more accurate answers.

Connect data sources

Add Grafana, Kubernetes, and more to power investigations.