{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/observability.error-to-fix/",
    "json": "https://www.anchorterminal.com/niches/observability.error-to-fix/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/observability.error-to-fix/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/observability.error-to-fix/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 3 | 13 | 20 | 10 |\n\n## What counts as done\n\nFor each chosen issue: the full stack trace, affected-user count and first and last seen time retrieved, the source file located, and either a pull request or a written reason for not fixing it.\n\nHow agents ask for it: fix the top Sentry issues; what is this error and where in the code; open a PR for this crash; which errors affect the most users\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Sentry MCP (Functional Software, Inc. d/b/a Sentry)**: get_issue_details, get_event_stacktrace (full trace per thread), get_issue_breadcrumbs and find_releases cover the issue; acc-02 runs top-issues-by-users to a pull request. Whether resolved source links are now in the payload (#1157, closed) wasn't confirmed.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **Better Stack (Better Stack, Inc.)**: List errors gives affected users and state, Get error details gives call site and first occurrence, releases give first and last seen; the full trace needs an exceptions query, and resolved source links are not documented.\n- **Datadog MCP Server (Datadog, Inc.)**: The error-tracking toolset searches and reads Error Tracking Issues and counts errors by version in SQL, but the docs do not show whether the issue read carries the full stack trace, affected users or source links.\n- **New Relic MCP Server (New Relic, Inc.)**: list_entity_error_groups and get_error_statistics give error groups with counts and first and last seen, and search_errors returns raw events, but the docs don't say whether full stack frames, affected users or source links come back.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Cronitor MCP server (Cronitor)**: list_site_errors and get_site_error exist, but the docs leave their fields to tools/list behind sign-in, so stack depth, affected users and first and last seen could not be read.\n\n- not this job: Axiom MCP Server (Axiom, Inc.): No error-tracking issue object: no grouped issue, affected-user count, first and last seen or source-linked frames. Stack traces exist only if the app logged them, and the agent would compute the rest in APL.\n- not this job: Causely MCP server (Causely, Inc.): Diagnoses list exceptions as evidence, but no tool returns a full stack trace, affected-user count or first and last seen time per error.\n- not this job: Grafana MCP Server (Raintank Inc., d/b/a Grafana Labs): No error-tracking issue object: no grouped errors, affected-user counts, first and last seen or source-linked frames.\n- not this job: Honeycomb MCP (Hound Technology, Inc. d/b/a Honeycomb): No error-tracking issue object: no grouped errors, affected-user count, first and last seen or source-linked frames.\n- not this job: incident.io API (Pineapple Technology Ltd.): No error-tracking data: no stack traces, affected-user counts or first and last seen per error.\n- not this job: PagerDuty MCP Server (PagerDuty, Inc.): No error-tracking data or stack traces.\n- not this job: Rootly MCP Server (Rootly Inc.): No error-tracking data or stack traces.\n\n## What stops agents finishing\n\n- stack trace or code-mapping link missing from the API payload\n- OAuth-only hosted endpoint with no headless route\n- single dispatcher tool hides writes from host approval\n\n## Around it\n\nBefore: observability.scheduled-watch, notifications.alert-received. After: code.open-pr, project-management.create-ticket.\n\n## Where this comes from\n\nWeight 20 of 100 in Observability \u0026 incidents: 10 of 42 accounts; Sentry dominates (9 of 10), so this weight describes Sentry users more than the category\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/observability.error-to-fix.json, or the MCP tool get_use_case with id observability.error-to-fix. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Triage production errors and turn them into a code fix",
        "url": ""
      }
    ],
    "description": "Triage production errors and turn them into a code fix: 1 companies fully do it, 3 with a limit, 13 carry the tag. Every listing in Observability \u0026 incidents with the reason and a source.",
    "facts": null,
    "h1": "Triage production errors and turn them into a code fix",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/observability.error-to-fix/",
    "published": "",
    "section": "agents",
    "title": "Triage production errors and turn them into a code fix | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/observability.error-to-fix/"
  },
  "tokens": {
    "markdown": 1250,
    "slim": 280
  },
  "version": 1
}
