Investigate an alert
Go from a firing alert to monitoring evidence, Investigation Insights, and Possible Causes.
On this page
When an alert fires, start an investigation from it. FixBugs queries your monitoring for evidence around the alert, reads your code with that evidence, and gives you Investigation Insights and Possible Causes. You can see and change every query before it runs again.
Before you start
- FixBugs installed and signed in. See Quickstart.
- The repository the alert belongs to, open as a folder in VS Code.
- An Alertmanager, Sentry, Grafana, or Grafana Cloud account, and a read-only token for it.
Connect an alert source
Connect each monitoring source once; every investigation can use it. FixBugs keeps the token in your editor's secret storage on your machine.
- On the FixBugs home, select Set up alert source. Alert Sources opens.
- Under Add a provider, choose
alertmanager,sentry,grafana, orgrafana_cloud. - Select Add source. The connect form opens.
- Enter a Display name and the Provider URL.
- For Sentry, enter the Organization slug and Project slug. For Grafana or Grafana Cloud, choose Use default organization or Use organization ID.
- Paste the token into Read-only provider token.
- Select Connect source. The source appears under Configured sources.
A source marked Ready is connected. If it shows Pending confirmation, select Verify.
Catalog Window (days) sets how many days of alerts FixBugs keeps for browsing: 1 to 60, 10 by default. An alert that is still firing stays listed whatever its age. To change it, enter the number of days and select Apply.
Find the alert
- On the FixBugs home, select View Active Alerts. Active Alerts lists the alerts your sources report as firing.
- To narrow the list, use the filters: Time, Severity, Provider, Source, Alert name, and Search (text in the alert; press Enter).
- Select an alert. Its details open.
- Select Investigate. FixBugs creates the investigation for the first folder open in VS Code and opens it.
Browsing Active Alerts collects no evidence and starts no work. To reload the list, select Refresh.
Enter an alert yourself
If the alert is not in Active Alerts, describe it by hand.
- On the FixBugs home, select Investigate Alert. Investigate an alert opens.
- Under Repository, select Current workspace, or point FixBugs at another copy of the code.
- Under Alert identity, choose the Provider and Alert type.
- Enter the Alert ID, the Title, and Alert observed at.
- Optional: paste the alert's link into Source URL. If FixBugs asks for a Monitoring source, choose a connected source for that provider.
- Optional: under Work request (optional), tell FixBugs what you want from the investigation.
- Select Start alert investigation. The investigation opens.
If the button is unavailable, the line next to it says what is missing.
Start the investigation
The investigation page shows the alert, its time window, the code revision FixBugs resolved, and the Monitoring sources it will query.
- If no source is listed, select Add monitoring source and connect one.
- Select Continue investigation. FixBugs drafts an Evidence acquisition plan and starts the queries. Acquisition progress counts the finished queries.
Review the evidence acquisition plan
The plan lists each query FixBugs runs against your sources: the query text and its time window. Changes you make are proposals; nothing changes until you accept one.
To edit the queries yourself:
- Select Edit plan.
- Change a Query expression, Query start, or Query end.
- Select Propose changes. The proposal appears under Proposals awaiting review.
To have the Assistant redraft the plan:
- Select Regenerate with Assistant.
- Optional: under Guidance (optional), say what to look for.
- Select Generate proposal. The proposal appears under Proposals awaiting review.
To act on a proposal:
- If queries are still running, select Pause acquisition to apply changes. FixBugs pauses at its next checkpoint.
- Review the changes listed under the proposal.
- Select Accept revision on the proposal, or Decline to keep the current plan.
- If Resume acquisition appears, select it. FixBugs runs the accepted revision.
If you accept a new revision after the analysis has run, FixBugs analyzes again with the new evidence.
If the evidence FixBugs keeps reaches the Approved limit, the queries pause. Enter a New limit (GiB) and select Approve higher limit, or select Keep paused.
When evidence is missing
If some queries fail and others return evidence, FixBugs continues with the evidence it has.
If no query returns usable evidence, FixBugs shows Monitoring evidence unavailable, with the number of usable observations, failed queries, and missing signals, and the reason for each source. Choose one:
- Edit source: correct the source's URL or token.
- Retry: run the same queries again, for example after a provider outage.
- Proceed anyway: investigate without monitoring evidence. Enter your reason, then select Proceed anyway.
FixBugs shows only the choices that apply to the failure.
If the analysis itself fails, FixBugs shows Analysis needs attention. The evidence is kept. Fix your model access or execution mode under Execution settings, then select Retry analysis.
Read Investigation Insights and Possible Causes
When the evidence is in, FixBugs analyzes it with your code. Use the workflow steps at the top of the investigation:
- Select Analysis. Investigation Insights summarizes what FixBugs learned from the alert, the evidence, and your code.
- Select Hypothesis. Possible Causes lists what FixBugs believes is wrong and why.
FixBugs continues to a Plan and a Fix. Nothing changes in your workspace until you select Apply Fix.
Open the investigation board
To see the evidence side by side in a browser, select Open investigation board. The board shows the evidence, the evidence acquisition plan, and the query results. It is read-only: you make changes in VS Code. To reload it, select Refresh investigation. The board closes when FixBugs stops.
Next steps
- Choose your models: pick which models run the investigation.
- Plans & pricing: what counts as a fix.