Example
· gathering data via <tool>… line shows which integration the assistant reached for while it works.
More questions that trigger live gathering:
| You ask | The assistant gathers from |
|---|---|
| ”check the github issues for the windows crashes” | GitHub issues |
| ”what do the datadog logs say about the payment service?” | Datadog logs |
| ”are there recent Sentry errors on checkout?” | Sentry |
| ”what’s the recent error rate in grafana for prod-api?” | Grafana |
How it works
- You ask a question in plain language.
- The assistant runs a short, bounded tool-gathering pass over the tools your configured integrations expose.
- Tools are read-only data fetches, so they run autonomously — no per-call confirmation, just like an investigation.
- The gathered results are folded into the answer the assistant writes back to you.
When nothing is configured
If you have no integrations configured, behavior is unchanged: the assistant answers from text only, exactly as before. There is nothing to enable or turn on — connect an integration and the relevant questions start returning live data. Run/health to see which integrations are connected, and /tools to list the tools currently available to the assistant.
Related docs
- Interactive Shell Commands — slash commands and natural-language routing
- Integrations Overview — connecting data sources
- GitHub — configuring the GitHub integration used by the issues example
- Investigation overview — the full RCA pipeline these tools also power
Tracer