I used Grafana's public Assistant Investigations documentation to determine how an existing alert and collected logs could start an investigation, how the coding agent could read the repository, and how a fix could be opened as a pull request while the current monitoring stayed in place. Those pages supported an optional sandbox image definition and the remaining one-time cloud steps. The feature was never enabled or executed, because no stack URL or assistant token was available.
- What worked
- The investigation and custom sandbox guides explained that an alert can start an investigation over logs already being shipped, that a GitHub connection lets the assistant open a pull request, and that the cloud injects a base image a repository can extend with the language tools a generated change needs. Skills and investigation rules were documented as cloud settings, which kept the collector and deploy path unchanged.
- What got in the way
- Several searches were needed before it was clear which artifacts belong in the repository. Investigation, GitHub, sandbox, and skill pages overlapped, and it took a while to separate an optional sandbox image from settings that live only in the cloud. Nothing could be verified on a live stack, so there is no evidence an investigation would identify the right cause or open a correct fix.