webhook: {source: alerting}, so turning it on connects it to your organization’s alerts (Webhooks).
Before you begin
- A Forge project deployed to a hosted environment, which gets the default alert rules and error issues (Hosting overview).
- The Reliant GitHub App installed on the repository the issues should go to (GitHub integration).
- A machine that can hold a checkout of that repository.
- The
reliantCLI v1.21.3 or later, signed in, or the app.
Put the repository's checkout in a Reliant project
<project>/<repo name>, or the project folder itself, whose origin is the alert’s repository. Without one, the issue is filed but not investigated.forge.yaml names, and of environments deployed from repositories it holds.Check the workflow's behaviour before it runs for real
same_fingerprint_dedupes shows a re-sent alert getting a comment, and search_failure_is_not_treated_as_new that it files nothing when it cannot rule out a duplicate (scenario format).Turn on-call on
service_repos maps an alert’s service label to a repository; default_repo takes the rest, or leave it empty to ignore unmapped alerts. Other settings are in Autopilot on-call settings.Confirm it is connected to your alerts
critical and error alerts, plus the error and release alerts at any severity, from every environment of this project that raises alerts (persistent ones Reliant hosts and self_managed ones such as an environment forge obs init registered), not previews. Your other receivers are unchanged.Make an alert fire
TypeError on every page view; within minutes it was an issue with a firing NewIssue alert:Check the issue it filed
agent:triage:- Title:
[error] <service>: <error title>or[alert] <alertname>: <summary>, then the prefix plus the investigator’s one-line summary. - Body: severity, confidence, the key it deduplicates on (an error’s issue id or an alert’s fingerprint), then Summary, Evidence, Suspected cause and Proposed fix.
Decide what happens next
agent:triage until a person acts on it:- Have an agent fix it: replace
agent:triagewithagent:ready. If the issue worker is on for that repository, it writes a failing test and the fix, and opens a pull request for you to review and merge. - Fix it yourself, or close it as noise. A later alert with the same key opens a new issue only once this one is closed.
Turn it off when you are done
--project-id it pauses every project’s on-call. Pausing or deleting removes the alert receiver.What this does not do
- It does not fix or merge anything. On-call only files and comments; its investigator has no edit tools, no GitHub write tools and a shell with no credentials. Alert to fix is two linked steps with a person at each gate: a person labels the issue
agent:ready, the issue worker opens a pull request, and a person merges it. Autopilot never addsagent:readyand never merges. - It does not read your logs or traces. For an error it gets the service, title, culprit, first build and a console link, works from those and the code, and says what it could not reach.
- It does not see every alert. Other warnings, preview environments and silenced alerts never reach it. By default it investigates five new alerts per notification (
max_investigations) and files the rest without a write-up. - It does not page anyone. It runs beside your Slack, PagerDuty or email receivers.
Troubleshooting
no project workflow is named "autopilot-oncall"
no project workflow is named "autopilot-oncall"
--workflow builtin://autopilot-oncall.No checkout of acme/app was found under …, so … was filed but not investigated
No checkout of acme/app was found under …, so … was filed but not investigated
<project>/<repo name> or the project root, or its origin points elsewhere. Clone it there.on-call: none of the 1 alert(s) has a usable fingerprint and a repository in service_repos / default_repo, so nothing was filed.
on-call: none of the 1 alert(s) has a usable fingerprint and a repository in service_repos / default_repo, so nothing was filed.
service_repos key matched and default_repo is empty. Run reliant trigger activate again with new --params-json.No firings yet.
No firings yet.
obs status shows an alert firing but reliant trigger events lists nothing. Check the alert passes the filter (step 4) and that obs receivers list shows the autopilot-<activation id> receiver. If its env_kinds is persistent alone, it was created before self-managed environments were included: pause and resume the activation to recreate it with the current filter. Pausing and resuming the activation connects its receiver again. NewIssue fires once per issue, so test again with a new error.Next steps
Autopilot: alerts and errors
Go from a production error to a reviewed fix
Dashboards and alerts
Webhooks
source: alerting trigger, and self-hosted Alertmanager.