- TRIAGE
- ANALYSIS
- CONTEXT
- HUMAN
Short answer
How can my AI help me find the cause of a production outage?
Your agent pulls recent system events and specific error logs from Guance Cloud to pinpoint the source of a failure. It correlates these data points to show you exactly what triggered the outage. You get a clear path to the root cause.
Incident outcomes.
Where every issue lands.
What your agent delivers after analyzing the telemetry.
TRIAGE
Identified event clusters
The agent uses list_events to group recent system anomalies. You see exactly which services are failing.
ANALYSIS
Pinpointed error details
By pulling specific logs, the agent finds the exact stack trace or error message. This removes the guesswork from the investigation.
CONTEXT
Log source mapping
The agent identifies which log sources are reporting issues. This tells you which specific infrastructure components are involved.
HUMAN
Decision support
The agent presents the evidence, but you decide whether to roll back a deployment or scale a cluster. It handles the digging so you can handle the fix.
The workflow
What your AI does when an incident occurs.
The agent automates the tedious data gathering phase of incident response.
Scan for recent anomalies
The agent looks for any recent system events that coincide with your alert timestamp.
list_eventsIsolate specific errors
Once an anomaly is found, the agent pulls the full details of that specific event to see the error message.
get_eventMap the log landscape
The agent checks which log sources are active to ensure it isn't missing data from a specific microservice.
list_log_sourcesSynthesize the root cause
The agent combines the event data and log details to explain why the system is failing.
get_event
Try it
Copy these to start.
Use these prompts to kick off an investigation.
Starting points
These are opening lines. Swap out the service names or timeframes to match your actual outage.
Guance Cloud / 观测云 Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_AANzdKMqG2pZyVDyBezhkEvdo4gPXGC9YiQz8RcU/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — Guance Cloud / 观测云 capabilities are ready to use.
{
"mcpServers": {
"guance-cloud-mcp": {
"url": "https://edge.vinkius.com/vk_preview_AANzdKMqG2pZyVDyBezhkEvdo4gPXGC9YiQz8RcU/mcp"
}
}
}List the most recent system events in Guance Cloud from the last 30 minutes.
Get the details for the error event related to the checkout-service.
Show me all log sources currently reporting data in Guance Cloud.
Based on the recent events, what is the likely cause of the latency spike in the production cluster?
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect Guance Cloud once, then ask.
One connection gives your agent access to your telemetry. Your credentials stay encrypted and secure.
Connect Guance Cloud to your AIFAQ
How this task behaves.
- 01
Can the AI fix the production issue automatically?
No. The agent only reads event and log data to provide context. You must perform the actual remediation.
- 02
Does the AI have permission to delete logs?
No. The tools only allow the agent to list and get event data. It cannot modify or delete any data in Guance Cloud.
- 03
Can I use this with any AI client?
Yes, as long as the client supports the Model Context Protocol (MCP).
- 04
How does the AI know which logs to look at?
It uses the list_log_sources tool to see what is available and then targets specific events to find relevant details.
- 05
Will the AI see all my system data?
The agent only sees the data it explicitly requests through the provided tools during your conversation.
More questions about Guance Cloud? The Connector page answers them. See everything the Guance Cloud Connector can do
Connect Guance Cloud / 观测云 to Claude, Cursor, ChatGPT & more
