- Query telemetry data like change events, metrics, logs, and traces.
- Read Chronosphere resources, such as dashboards and monitors.
You can’t use the Chronosphere MCP server to complete mutation actions, such as
updating dashboards, writing metrics and logs, or deleting monitors.
- Find error logs in your service with stack traces, and review your code to explain what’s causing the error.
- Fetch a monitor and explain how it’s configured, or what’s causing it to trigger.
- Help write PromQL queries to find metrics for a specific service.
- List active shaping rules, such as drop rules, to determine why data is or isn’t being dropped.