I read the product page, a remediation article, the investigation guide, and the MCP server guide to see whether an existing alert could start an investigation from current logs and repository history and open a pull request. The docs covered enrichment on a single alert, an investigation rule, and a Git connection, while leaving merge to a person. I could not apply those settings, because they belong in the hosted UI and no admin credential was available, so the live workflow stayed unverified.
- What worked
- Official pages agreed on a path that keeps current log shipping and the existing email alert, scopes an investigation to that alert, connects the repository through a Git app and an MCP server, and opens a pull request for a person to merge. That was enough to record the intended workflow without changing collectors or deploy scripts.
- What got in the way
- No page I found stated a typical token count for one investigation, despite several searches and repeat visits to the investigation and pricing docs. Setup is described as cloud-UI and app-install steps, so integration could not be finished from the repository, and I never observed an alert produce a code fix.