Niches · Observability & incidents
Find the cause of an alert or incident across metrics, logs and traces
Four or more companies' docs show a full fit.
What counts as done
A short report naming the likely cause, the queries or evidence behind it (series, log lines or trace ids with timestamps) and the time window, built only from read calls.
Measured, for our own tests: report within 15 minutes and 30 tool calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: why did this alert fire
, why is the app slow
, debug this incident
, what changed before latency went up
Does the job 8
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Axiom MCP Server BB Axiom, Inc. | queryDataset takes APL and queryMetrics takes MPL directly; getMonitorHistory and services-getChanges give the alert and what changed; query cost limits return a 429 naming the limit. Accounts acc-15 and acc-16 describe agents finding traces and alerts this way. source |
| Better Stack C Better Stack, Inc. | Execute query runs ClickHouse SQL over logs, spans, metrics and exceptions; incident details and timeline give the alert; Plan query windows splits long ranges; a Read token keeps it to reads. acc-14 uses it daily to resolve reported errors. source |
| Causely MCP server E Causely, Inc. | get_alerts, investigate_alert, get_issues and get_diagnosis_details return the inferred cause with causal chain, blast radius, logs, exceptions and events, and get_diagnoses takes a start and end window; all reads. source |
| Datadog MCP Server D Datadog, Inc. | Core toolset searches logs, spans, metrics, monitors and events with Datadog query syntax, analyze_datadog_logs takes SQL, and get_datadog_trace follows a trace. Accounts acc-05, acc-06 and acc-07 describe agents debugging production this way. source |
| Grafana MCP Server BB Raintank Inc., d/b/a Grafana Labs | PromQL, LogQL and TraceQL tools take native queries, alerting_rules_read and OnCall alert groups give the alert, get_tempo_trace follows a trace id, and --disable-write keeps it to reads. acc-08, acc-11 and acc-12 run incident work this way. source |
| Honeycomb MCP B Hound Technology, Inc. d/b/a Honeycomb | run_query takes a Honeycomb query spec, get_triggers gives the alert, get_trace follows a trace id and run_bubbleup isolates what differs, all read tools. acc-09 and acc-10 describe alert and regression investigations that return a full report. source |
| New Relic MCP Server B New Relic, Inc. | execute_nrql_query takes NRQL directly; search_incident, list_recent_issues and list_change_events give the alert and what changed; search_errors takes a trace id and get_distributed_trace_details follows it. The server is read-only by scope. source |
| Sentry MCP B Functional Software, Inc. d/b/a Sentry | search_errors, search_traces and search_logs, get_trace_details and get_sentry_resource with an issue or trace URL give errors, traces and logs with ids; find_metric_monitors gives the alert. acc-05 and acc-16 use it for incidents and inbound alerts. source |
Does the job, with a limit 4
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Cronitor MCP server C Cronitor | get_status, list_issues and get_metrics show which job, heartbeat or check failed and its latest event, but there are no logs or traces, so causes outside the monitored job are out of reach. source |
| incident.io API B Pineapple Technology Ltd. | alert_show, incident_show and investigation_sync give the alert, linked incidents and findings, but telemetry is reached only through ask_telemetry, a natural-language agent that needs the Investigations product, so queries and series are not the agent's own. source |
| PagerDuty MCP Server E PagerDuty, Inc. | browse_incidents lists alerts, notes, change events and related or past incidents, but PagerDuty holds no metrics, logs or traces, so the cause needs another server. source |
| Rootly MCP Server C Rootly Inc. | core and alerts toolsets read incidents and alerts, and an observability toolset reads Rootly Observability logs and patterns; there are no metrics or traces, and logs exist only for teams on Rootly Observability. source |
What stops agents finishing
- the relevant signal was never collected
- agent misreads which layer an alert belongs to
- query-cost or rate cap reached mid-investigation
- tool list fills the context before the first query
Around it
Before: notifications.alert-received, messaging.slack-thread, observability.oncall-and-incident-records. After: code.open-pr, observability.oncall-and-incident-records, messaging.post-summary.
Where this comes from
Weight 26 of 100 in Observability & incidents: 13 of 42 accounts (about 26 per cent of the 50 account-to-use-case links); the job most often described in the Ask HN MCP-in-production thread and the SRE threads
The same as data: /api/v1/use-cases/observability.investigate-alert.json, or the MCP tool get_use_case with id observability.investigate-alert. Other jobs in this category: /api/v1/niches?category=observability.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.