# Create dashboards, monitors and instrumentation

> Create dashboards, monitors and instrumentation: 0 companies fully do it, 7 with a limit, 15 carry the tag. Every listing in Observability & incidents with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/observability.build-dashboards-monitors/
- Markdown: https://www.anchorterminal.com/niches/observability.build-dashboards-monitors/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/observability.build-dashboards-monitors/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/observability.build-dashboards-monitors/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 7 | 15 | 8 | 4 |

## What counts as done

A dashboard, monitor or alert rule that the tool's API accepts and validates, returned with its id and link, and showing data for the chosen series on a re-read.

How agents ask for it: build a Grafana dashboard for this service; add a monitor for this cron job; set up alerting on error rate; add the tracing we were missing

## Does the job, with a limit

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.

- **Axiom MCP Server (Axiom, Inc.)**: createDashboard, replaceDashboard, updateDashboardChart and createMonitor exist, but the docs show neither the returned id and link nor the error for an invalid chart or threshold; non-email notifiers need the console.
- **Better Stack (Better Stack, Inc.)**: Create dashboard, Add chart to dashboard, chart alerts and Create monitor exist and dashboards list with ids, but the MCP docs show no validation error or returned link for a chart.
- **Cronitor MCP server (Cronitor)**: setup_monitor upserts by stable key and returns the key and monitor_url, but over the plan's monitor limit the monitor is saved disabled, a blocker the map names. No dashboards.
- **Datadog MCP Server (Datadog, Inc.)**: upsert_datadog_dashboard with validate_dashboard_widget, and validate_datadog_monitor before create; but monitors are created as drafts a person publishes in the UI, and the returned link is not documented.
- **Grafana MCP Server (Raintank Inc., d/b/a Grafana Labs)**: update_dashboard, patch dashboard, alerting_rules_write and generate_deeplink cover build, id and link, but full dashboard JSON is costly: acc-22 burned 14 million tokens on one Grafana dashboard.
- **Honeycomb MCP (Hound Technology, Inc. d/b/a Honeycomb)**: create_board, create_trigger and create_slo exist, and create_slo validates the SLI expression, but the docs show neither the returned id and link nor an invalid-threshold error.
- **Sentry MCP (Functional Software, Inc. d/b/a Sentry)**: create_alert_rule, create_metric_monitor and create_uptime_monitor exist, but returned ids, links and validation errors were not read, and dashboards are read-only (find_dashboards, get_dashboard_details).

- not this job: Causely MCP server (Causely, Inc.): No dashboard or alert-rule tools; configuration tools only set thresholds, SLO targets and service tiers.
- not this job: incident.io API (Pineapple Technology Ltd.): No dashboard, monitor or alert-rule tools.
- not this job: New Relic MCP Server (New Relic, Inc.): Only list_dashboards and get_dashboard; the OAuth scope is observability:read and no create tools exist.
- not this job: PagerDuty MCP Server (PagerDuty, Inc.): No dashboard or monitor tools; alert grouping and event orchestration rules are routing, not monitors.
- not this job: Rootly MCP Server (Rootly Inc.): No dashboard or monitor tools; heartbeats and alert routes are alert intake, not monitors over series.

## What stops agents finishing

- dashboard JSON so large that one build burns millions of tokens
- monitor saved but disabled over the plan's limit (Cronitor)

## Around it

Before: observability.investigate-alert, code.read-repo. After: observability.scheduled-watch.

## Where this comes from

Weight 8 of 100 in Observability & incidents: 4 of 42 accounts; none used a listed MCP for the write (Grafana dashboards built by Claude from code or the API)

As data: https://www.anchorterminal.com/api/v1/use-cases/observability.build-dashboards-monitors.json, or the MCP tool get_use_case with id observability.build-dashboards-monitors. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
