Investigate telemetry incidents with Monoscope MCP and agent-mode CLI
Connect agents to Monoscope so they can query logs, traces, metrics, monitors, and issues through stable JSON CLI output or MCP tools for incident triage.
npx skills add agentskillexchange/skills --skill investigate-telemetry-incidents-with-monoscope-mcp-and-agent-mode-cli
Use Monoscope when an agent needs to investigate observability data, triage incidents, or produce operational reports from logs, traces, metrics, monitors, and issues.
What this skill actually does
The workflow is to self-host or use Monoscope cloud with S3-backed telemetry storage, ingest OpenTelemetry data, enable the CLI in agent mode or connect an MCP-capable client to the Monoscope MCP endpoint, then let the agent run structured searches, fetch event context, analyze issues, acknowledge monitors, and generate incident summaries or daily/weekly reports.
This is not just an observability platform listing. The boundary is agent-driven telemetry investigation: stable JSON command envelopes, MCP tools, natural-language to query workflows, issue analysis, monitor management, and scheduled anomaly/report agents. It should be invoked for repeatable on-call sweeps and incident triage, not for ordinary dashboard browsing alone.
Inputs and prerequisites: Monoscope cloud or self-hosted stack, S3-compatible storage, OpenTelemetry or test telemetry data, Monoscope CLI or MCP-capable client, API key for MCP access.
Setup notes: Clone https://github.com/monoscope-tech/monoscope and run docker-compose up for self-hosting, or use Monoscope cloud. Install the CLI with the upstream install script and set MONOSCOPE_AGENT_MODE=1 for JSON output, or configure the MCP endpoint at https://api.monoscope.tech/api/v1/mcp with an Authorization header.
Source and verification boundary: use https://docs.monoscope.tech as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.