Honeybadger vs GlitchTip

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Honeybadger
   Honeybadger✓fullprobed8/10

   Honeybadger has a confirmed llms.txt endpoint (HTTP 200) plus dedicated _llms-txt reference docs (product-reference.txt, insights-reference.txt, other-reference.txt) that an agent can be pointed at, and also offers a documented MCP server as an agent-facing integration. missing for 10: independent/hands-on confirmation that an agent actually consumes llms.txt successfully, and no discoverable machine-readable OpenAPI spec to complement it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.honeybadger.io/llms.txt # Honeybadger.io > Honeybadger provides error tracking, uptime monitoring,…”
   • [claimed-docs] “You can create additional accounts and switch between accounts using the dropdown in the navigation bar.”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

   GlitchTip—none0/10

   Direct probes confirm llms.txt (404) and machine-readable docs/openapi endpoints (404) are absent; while GlitchTip has an MCP server, there is no evidence of an llms.txt file or agent-oriented documentation format that an agent could be pointed at.

   • [probe] “PROBE llms.txt: HTTP 404 at https://glitchtip.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://glitchtip.com/documentation.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to GlitchTip
   Honeybadger✓fullprobed6/10

   Honeybadger ships a CLI and REST API (e.g., `honeybadger deploy`, exceptions/deployments/source-map endpoints) explicitly designed for scripted, non-interactive use, which is exactly what's needed to invoke it headlessly from CI pipelines, and error/deploy tracking runs automatically once configured. Missing for 10: explicit CI/CD integration examples (e.g., GitHub Actions/GitLab CI snippets) and independent hands-on confirmation of CI usage.

   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “`honeybadger deploy` Notify Honeybadger of deployment”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

   GlitchTip✓fullprobed7/10

   GlitchTip ships an official CLI (glitchtip-cli) with commands for login, creating releases, recording deployments, and uploading debug files/source maps — all standard headless CI automation tasks (e.g. glitchtip-cli releases new 1.0.0 --org --project, glitchtip-cli deploys new). This directly supports scripted/CI use even though it's framed as error-tracking tooling rather than an agent runtime. Missing for 10: explicit CI/CD pipeline examples (e.g. GitHub Actions/GitLab CI snippets), independent community confirmation of CI usage, and no evidence of a broader headless server/automation mode beyond the CLI.

   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”
   • [claimed-docs] “Record deployments for a release: glitchtip-cli deploys new 1.0.0 --env production --org my-org --project my-project”
   • [claimed-docs] “Upload debug symbols for native applications (dSYM, PDB, ELF): glitchtip-cli debug-files upload ./build --org my-org --project my-project”
   • [claimed-docs] “Log in to your GlitchTip instance: glitchtip-cli --url https://your-glitchtip.example.com login”
   • [probe] “official CLI documented at https://glitchtip.com/documentation/cli”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Honeybadger
   Honeybadger✓fullprobed9/10

   Honeybadger ships an official hosted MCP server (docs.honeybadger.io/resources/mcp/) that lets an AI assistant connect and gain project management, error investigation, and Insights/BadgerQL query capabilities, with OAuth-based connection flow documented in the changelog. This is first-party documentation of exactly the described capability, though missing for 10: independent/hands-on verification of the MCP server working in practice.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “Our hosted MCP server supports OAuth, so you can connect an agent by approving access in your browser instead of copying and pasting a crede…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

   GlitchTip✓fullprobed8/10

   GlitchTip documents a built-in, official MCP server enabling AI assistants to interact with error tracking, performance, and log data, with specific tools like investigating errors and detecting N+1 queries. This is first-party documented and confirmed by a dedicated docs page and probe. Missing for 10: independent/hands-on community corroboration of the MCP server working in practice, and more detail on setup/authentication.

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “detect_n_plus_one — Detect N+1 query patterns across transactions (requires DuckDB)”
   • [probe] “official MCP server documented at https://glitchtip.com/documentation/mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Honeybadger
   Honeybadger✓fullprobed6/10

   Honeybadger ships an official CLI (Ruby gem) documented with commands like `honeybadger deploy` for notifying deployments and other utilities, confirmed by docs and probe. It exists as a first-party tool a script or AI agent could invoke, though it is narrow in scope (deployment notification, limited to Ruby ecosystem) and not marketed as AI-native. Missing for 10: broader multi-language CLI coverage, AI-specific CLI features/flags, and independent/hands-on confirmation of agentic usage.

   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “`honeybadger deploy` Notify Honeybadger of deployment”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

   GlitchTip~partialprobed6/10

   GlitchTip ships an official glitchtip-cli with documented commands for login, releases, deployments, and debug-file uploads, confirmed by dedicated CLI docs and a probe. However, it's explicitly framed around release/source-map management rather than general agentic/AI-native workflows, and the CLI itself is separate from the MCP server (the AI-facing feature); no independent hands-on reviews of the CLI were found. Missing for 10: independent/community verification of the CLI's reliability, evidence of AI-native or agentic use cases for the CLI specifically, and confirmation it's out of beta.

   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”
   • [claimed-docs] “Record deployments for a release: glitchtip-cli deploys new 1.0.0 --env production --org my-org --project my-project”
   • [claimed-docs] “Upload debug symbols for native applications (dSYM, PDB, ELF): glitchtip-cli debug-files upload ./build --org my-org --project my-project”
   • [claimed-docs] “Log in to your GlitchTip instance: glitchtip-cli --url https://your-glitchtip.example.com login”
   • [probe] “official CLI documented at https://glitchtip.com/documentation/cli”
   • [claimed-docs] “For JavaScript projects, upload source maps to get readable stack traces. Use the GlitchTip CLI (Beta) to inject debug IDs and upload source…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Honeybadger
   Honeybadger✓fullprobed8/10

   Honeybadger exposes a well-documented public REST API for reporting exceptions, source maps, deployments, and querying faults (docs-15,16,17,19,36), plus a CLI (docs-18,31) and MCP server (docs-13,30) enabling AI agents to interact with it programmatically. No formal OpenAPI/Swagger spec was found via probe, slightly limiting machine-readable discoverability. Missing for 10: a discoverable OpenAPI/Swagger spec and independent third-party confirmation of API robustness.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “`honeybadger deploy` Notify Honeybadger of deployment”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

   GlitchTip~partialprobed5/10

   GlitchTip claims Sentry API compatibility (docs-11) and ships a documented CLI (docs-5,21,22,27) and an MCP server explicitly built for AI assistants to query error/performance/log data (docs-9,10,19,20), all supporting programmatic/AI-driven access. However, probes found no discoverable OpenAPI/Swagger spec or public API reference (probe-3), and no llms.txt (probe-1), so the actual 'documented public API' surface is thin and inferred mainly from SDK/CLI/MCP docs rather than a first-class API reference. Missing for 10: an explicit REST/GraphQL API reference doc, independent/community confirmation of API-driven automation, and resolution of the 404s on OpenAPI/swagger endpoints.

   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”
   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “detect_n_plus_one — Detect N+1 query patterns across transactions (requires DuckDB)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”
   • [probe] “official MCP server documented at https://glitchtip.com/documentation/mcp”
   • [probe] “official CLI documented at https://glitchtip.com/documentation/cli”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Honeybadger
   Honeybadger~partialprobed3/10

   Honeybadger's hosted MCP server supports OAuth-based approval flows for connecting an agent, which implies some access-control mechanism, but there is no documentation of issuing scoped or least-privilege API keys (e.g., read-only, project-restricted) specifically for agent use. missing for 10: explicit scoped/least-privilege API key creation, granular permission levels for agent credentials, documentation of restricting MCP/agent access to specific resources.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “Our hosted MCP server supports OAuth, so you can connect an agent by approving access in your browser instead of copying and pasting a crede…”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

   GlitchTip—none0/10

   GlitchTip documents an MCP server and CLI with login/org/project scoping, but there is no evidence of scoped or least-privilege API credential/token issuance specifically for agent use (e.g., read-only or capability-limited tokens for MCP/CLI); docs only describe org/project selection and general auth, not credential scoping. Missing for 10: documentation of granular/least-privilege API key or token scopes, any agent-specific credential model, or admin controls to restrict an agent's access.

   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “Log in to your GlitchTip instance: glitchtip-cli --url https://your-glitchtip.example.com login”
   • [probe] “official MCP server documented at https://glitchtip.com/documentation/mcp”
   • [probe] “official CLI documented at https://glitchtip.com/documentation/cli”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to GlitchTip
   Honeybadger~partialprobed6/10

   Honeybadger documents official client libraries/SDKs for multiple languages (Ruby, JS, Elixir/Oban) plus a public reporting/exceptions API, source-map API, and a Ruby CLI, giving AI-native builders concrete integration points (honeybadger-docs-1, -16, -24, -33, -18, -36). However there's no formal OpenAPI/swagger spec (404s on all candidate paths, honeybadger-probe-2) and no consolidated multi-language SDK catalog or independent hands-on confirmation of building against these SDKs. Missing for 10: a machine-readable API spec (OpenAPI), broader documented SDK coverage across major languages, and independent/community validation of SDK integration quality.

   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “Honeybadger now integrates with Oban (the Python port of the Elixir background job library). With this release you can report unhandled work…”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”

   proof ↗⚑ flag

   GlitchTip✓fullcommunity7/10

   GlitchTip officially documents that it works with Sentry's open-source SDKs and aims for full Sentry API compatibility, meaning developers build against the same official, widely-used SDK ecosystem; this is corroborated by community users who confirm reliable use of Sentry client libraries with GlitchTip in production. Missing for 10: GlitchTip-specific SDK documentation/language coverage list, and no independent verification of parity across all Sentry SDK versions/features.

   • [claimed-docs] “GlitchTip can use Sentry's open source SDKs to receive error data from your application.”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [community] “I use GlitchTip — it works well! A bit hard to deploy (many moving parts) but that's more a problem with F/OSS Sentry. It's been nice being …”
   • [community] “Hey Glitchtip! Been a happy user for going on a year or so. Super easy to self-host, and because it uses the existing sentry libs it's reall…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to GlitchTip
   Honeybadger~partialclaimed3/10

   Evidence confirms Honeybadger sends webhook requests (docs-25 mentions 'web hooks' alongside source maps and uptime checks with a secret token header), implying a webhook subscription mechanism exists, but no documentation details how to configure webhook endpoints, which events trigger them, or payload formats. Missing for 10: dedicated webhook setup/configuration docs, list of subscribable event types, payload schema examples, and independent confirmation of reliability.

   • [claimed-docs] “Requests sent from Honeybadger servers for source maps, web hooks, and uptime checks include the header Honeybadger-Token which is a secret …”

   proof ↗⚑ flag

   GlitchTip~partialclaimed6/10

   GlitchTip lets users add a webhook URL as an alert recipient so external systems can be notified of new errors/downtime pings, which satisfies the basic 'subscribe via webhook' capability. However, documentation is thin—no payload schema, event-type filtering, retry/delivery guarantees, or independent/hands-on confirmation of webhook use are provided. Missing for 10: webhook payload format documentation, granular event-type subscription options, delivery reliability details, and community corroboration of webhook usage.

   • [claimed-docs] “By default, new project alerts send emails to a project's team members, but you can also add a webhook URL by clicking “Add An Alert Recipie…”
   • [claimed-docs] “GlitchTip can ping your site and warn you when it's not responding. ... If GlitchTip doesn't receive your ping, it will send you an alert vi…”
   • [claimed-docs] “GlitchTip can ping your site and warn you when it's not responding. Or reverse it and send GlitchTip a request on schedule.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Honeybadger
   Honeybadger~partialprobed6/10

   Honeybadger offers AI-adjacent capabilities: natural-language-to-query search ('Describe your search' panel), anomaly detection against learned baselines, and an MCP server that lets an external AI assistant query BadgerQL/Insights data and help investigate issues. However, these are either query-assist/statistical alerting features rather than generative insight/suggestion output embedded directly in the product UI, or they require connecting an external AI agent via MCP rather than native in-product AI-generated insights. missing for 10: evidence of in-app AI-generated summaries/root-cause suggestions surfaced directly in the Honeybadger UI (not via external MCP client), and independent/hands-on validation of the natural-language search or anomaly detection quality.

   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

   GlitchTip~partialclaimed5/10

   GlitchTip's built-in MCP server lets external AI assistants query error, performance, and log data and includes analysis tools like detect_n_plus_one for pattern detection, which can surface AI-generated insights from the data. However, this is enabling external AI tools to analyze data rather than the product itself generating insights or suggestions natively inside its own UI. Missing for 10: in-product AI insight/summary generation, evidence of natively surfaced suggestions (e.g., root-cause hints) within the GlitchTip dashboard itself, and independent confirmation of MCP-driven insight quality.

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “detect_n_plus_one — Detect N+1 query patterns across transactions (requires DuckDB)”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Honeybadger
   Honeybadger~partialclaimed5/10

   Honeybadger ships several always-on background automations — Alarms (BadgerQL query + threshold triggers), anomaly detection against a learned baseline, check-ins for cron/scheduled jobs, and uptime monitoring — that run autonomously once configured. However, these are traditional monitoring rules rather than AI-agent-driven automations, and the MCP integration is scoped to investigation/query capabilities rather than configuring or running autonomous background workflows. Missing for 10: evidence that an AI agent can itself create/manage these background automations (e.g. via MCP or API), and any AI-specific autonomous workflow/task runner beyond monitoring alerts.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Check-ins Tracking pings from scheduled tasks and cron jobs”
   • [claimed-docs] “Uptime monitoring Get notified when your API and website are unresponsive”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”

   proof ↗⚑ flag

   GlitchTip—none0/10

   GlitchTip's automation is limited to built-in alerting (email/webhook on errors, uptime pings) and its MCP server is described only as a way to 'investigate' and query error data, not to configure or run autonomous background workflows on behalf of an AI agent. There is no evidence of an AI-driven automation/workflow builder or scheduled agentic tasks that a user could set up.

   • [claimed-docs] “GlitchTip can ping your site and warn you when it's not responding. ... If GlitchTip doesn't receive your ping, it will send you an alert vi…”
   • [claimed-docs] “GlitchTip can ping your site and warn you when it's not responding. Or reverse it and send GlitchTip a request on schedule.”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Honeybadger
   Honeybadger~partialclaimed3/10

   Honeybadger offers a narrow built-in AI feature — a 'Describe your search' panel that turns natural-language descriptions into BadgerQL queries — but this is a single-purpose assistant, not a general-purpose in-product AI agent you can delegate broader tasks to. The more prominent AI story here (MCP server, docs-13/30) is the reverse direction: it lets an external AI assistant (e.g., Claude) connect to Honeybadger, not a built-in assistant inside Honeybadger itself. Missing for 10: a general-purpose in-app AI assistant capable of multi-step task delegation, evidence of broader assistant capabilities beyond search-query generation, and independent/hands-on corroboration of this feature's usefulness.

   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”

   proof ↗⚑ flag

   GlitchTip—none0/10

   GlitchTip ships an MCP server so external AI tools/assistants can query its error data, but there is no evidence of a built-in AI assistant inside the product itself that a user could delegate tasks to — the direction is reversed (external AI pulls from GlitchTip, not GlitchTip offering its own assistant).

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Honeybadger~partialprobed6/10

   Honeybadger supports natural-language search via a 'Describe your search' panel that translates plain-language descriptions into BadgerQL queries, and its MCP server lets a connected AI assistant fetch data, run BadgerQL queries, and investigate issues conversationally. However, most core operations (deployments, alarms, integrations, CLI) still rely on structured queries/commands rather than direct natural-language control, and there's no independent evidence of how robust the NL search feature is in practice. Missing for 10: broader native NL command support across all product areas, independent/hands-on validation of NL search accuracy.

   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

   GlitchTip~partialprobed6/10

   GlitchTip ships a built-in MCP server that lets AI assistants browse issues, inspect stack traces/event data, resolve issues, and even detect N+1 query patterns, enabling natural-language interaction via connected AI tools rather than the raw UI. However, this is entirely first-party documentation with no independent/hands-on confirmation, and the documented scope is limited to investigation/read-type operations rather than full product control via NL. Missing for 10: independent verification of the MCP server working in practice, evidence of broader write/config operations (alerts, settings) via natural language, and any non-vendor usage reports.

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “detect_n_plus_one — Detect N+1 query patterns across transactions (requires DuckDB)”
   • [probe] “official MCP server documented at https://glitchtip.com/documentation/mcp”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Honeybadger—none0/10

   Docs describe static API endpoints (reporting-exceptions, faults, source maps) but there is no evidence of an interactive, runnable API reference/explorer; a probe explicitly found no OpenAPI/Swagger spec at any candidate URL (404s), indicating no such interactive documentation exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”

   proof ↗⚑ flag

   GlitchTip—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes explicitly show 404s for OpenAPI/swagger specs and no docs-as-markdown or llms.txt, and no mention of a sandboxed/try-it-out API explorer.

   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://glitchtip.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://glitchtip.com/documentation.md”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Honeybadger—none0/10

   The API is documented in prose (endpoints for reporting exceptions, faults, deployments, source maps), but a direct probe for machine-readable OpenAPI/Swagger specs at standard locations returned 404 across all candidates, and no evidence pack item links to a downloadable spec file. missing for 10: an actual OpenAPI/Swagger JSON or YAML file, any documented spec download link, or generator tooling.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence GlitchTip publishes an OpenAPI/Swagger spec; direct probes for openapi.json, swagger.json, and related paths all returned 404. Claims of 'Sentry API compatibility' do not constitute a machine-readable spec for GlitchTip itself.

   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Honeybadger—none0/10

   Evidence shows a documented REST API (v1/notices, faults, source maps, deployments) but no mention of API versioning scheme or a deprecation policy; the openapi.json probe returned 404s, suggesting no formal API spec is published. No evidence of version headers, changelog of breaking API changes, or deprecation timelines.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; probes for OpenAPI spec and docs manifest all 404'd, and no changelog/policy text addresses API stability or deprecation windows.

   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://glitchtip.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://glitchtip.com/documentation.md”

   proof ↗⚑ flag

Autofix

1. ai-native userThe platform's AI can draft a code fix for an error and open a pull request against my repo for human review

   weight 2 · round drawn
   Honeybadger—none0/10

   Honeybadger's MCP and integrations let an AI assistant investigate errors and query data, but there is no evidence of it drafting a code fix or opening a pull request against a repo. Missing for 10: any capability or documentation of AI-generated code fixes, automated PR creation, or git-write integration.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   GlitchTip's MCP server lets AI tools read error data (investigate issues, detect N+1 queries) but there is no evidence of AI drafting code fixes or opening pull requests against a repo; this is an error-tracking platform, not a code-fix automation tool.

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “detect_n_plus_one — Detect N+1 query patterns across transactions (requires DuckDB)”

   proof ↗⚑ flag

Root cause

1. ai-native userThe platform's AI analyzes an issue — stack trace, breadcrumbs, related commits — and proposes a root cause I can act on

   weight 3 · round to Honeybadger
   Honeybadger~partialprobed4/10

   Honeybadger's MCP server lets a connected AI assistant fetch error data, run BadgerQL queries, and 'analyze patterns to help investigate production issues' (docs-13, docs-30), which comes close to AI-driven root-cause analysis. However, this requires the user's own external AI client via MCP rather than a built-in platform AI that automatically correlates stack traces, breadcrumbs, and commits into a proposed root cause — no evidence of an integrated automatic root-cause feature exists. Missing for 10: evidence of a first-party AI feature (not just MCP data access) that ingests stack trace + breadcrumbs + commit history and outputs a concrete root-cause hypothesis, and any hands-on/independent validation of accuracy.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

   GlitchTip~partialprobed3/10

   GlitchTip ships a built-in MCP server that exposes stack traces, issues, and event data (including an N+1 query detector) to external AI tools, enabling an AI assistant to investigate an issue — but there is no evidence of GlitchTip itself analyzing breadcrumbs plus related commits to propose an actionable root cause; that analysis would rely entirely on whatever third-party AI client is plugged in via MCP. Missing for 10: native root-cause synthesis combining commits/breadcrumbs/stack trace, any documented example of an AI-generated root-cause suggestion, and evidence of commit/VCS integration feeding the MCP tools.

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “detect_n_plus_one — Detect N+1 query patterns across transactions (requires DuckDB)”
   • [probe] “official MCP server documented at https://glitchtip.com/documentation/mcp”

   proof ↗⚑ flag

Alert routing

1. sreRoute alerts by project, environment, and severity to Slack, PagerDuty, or email with per-rule thresholds — new issue, frequency spike, affected-user count

   weight 3 · round to Honeybadger
   Honeybadger~partialclaimed6/10

   Honeybadger docs show Slack and PagerDuty integrations, plus 'Alarms' that combine a BadgerQL query with a threshold (e.g., count > N) and anomaly detection for volume spikes, which covers frequency-spike-style alerting and routing to chat/on-call tools. However, there's no evidence of explicit per-project/per-environment routing rules, no documented email alert channel, and no dedicated 'affected-user count' threshold type distinct from generic query-based alarms — missing for 10: environment-based routing rules, email as a routing target, explicit affected-user-count threshold configuration, and severity-tiered rule matrices.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “You can generate an integration key for Honeybadger by logging in to PagerDuty then clicking on “Add New Service” and choosing “Honeybadger”…”

   proof ↗⚑ flag

   GlitchTip~partialclaimed3/10

   GlitchTip supports project-level alert routing (via teams) and basic recipients (email by default, plus adding a webhook URL), which could technically forward to Slack/PagerDuty, but there is no documented support for environment- or severity-based routing, nor per-rule thresholds like frequency spikes or affected-user counts. Missing for 10: environment/severity-based routing rules, native Slack/PagerDuty integrations, configurable thresholds for new-issue/frequency-spike/affected-user-count alerts.

   • [claimed-docs] “When making a project, you will also need to create a team if you have not already done so. Teams are for making sure the right people get n…”
   • [claimed-docs] “By default, new project alerts send emails to a project's team members, but you can also add a webhook URL by clicking “Add An Alert Recipie…”
   • [claimed-docs] “Teams are for making sure the right people get notified when an error is reported.”

   proof ↗⚑ flag

Noise control

1. sreFight alert fatigue with spike protection, per-key rate limits, and mute/ignore rules so one bad deploy doesn't page the whole team all night

   weight 2 · round to Honeybadger
   Honeybadger~partialclaimed4/10

   Honeybadger has real alert-fatigue tooling—error deduping/grouping, anomaly detection against a learned baseline, BadgerQL-based alarms with thresholds, and auto-resolve on deploy plus Slack resolve/reopen—but none of the evidence names the specific mechanisms in the story: spike protection, per-key rate limiting, or explicit mute/ignore/snooze rules for notifications. missing for 10: explicit spike-protection throttling, per-key/per-error rate limits, and a documented mute/ignore/snooze feature for alerts.

   • [claimed-docs] “Honeybadger groups identical errors together. Using our navigation bar, you can still navigate between each individual occurrence (or notice…”
   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   Evidence only shows basic alert routing (team notification emails/webhooks per project) and performance sampling via tracesSampleRate, but no mention of spike protection, per-key rate limiting, or mute/ignore/snooze rules for issues to combat alert fatigue.

   • [claimed-docs] “By default, new project alerts send emails to a project's team members, but you can also add a webhook URL by clicking “Add An Alert Recipie…”
   • [claimed-docs] “Teams are for making sure the right people get notified when an error is reported.”
   • [claimed-docs] “This rate can be set with the `tracesSampleRate` config option ... Set this to a low number like `0.01` to have your SDK send only 1 percent…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Honeybadger
   Honeybadger~partialclaimed4/10

   There's some evidence of bulk-like operations: deployments automatically mark all unresolved errors as resolved at once (docs-6, docs-29), and BadgerQL/Insights let users run aggregations and calculations across many events (docs-35, docs-8). However, there's no documented UI or API feature for explicit multi-select bulk actions (e.g., bulk resolve/delete/tag many errors at once) beyond the automatic deploy-triggered resolution. Missing for 10: explicit bulk-select UI/API endpoints for mass error management, documented batch operations beyond auto-resolve-on-deploy, independent confirmation of bulk workflows.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”
   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence of bulk operations (e.g., bulk resolve/delete/tag issues across many items) via UI, CLI, API, or MCP server; the CLI and MCP tools described operate on single releases/projects/issues, not bulk batches.

   ⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Honeybadger
   Honeybadger~partialclaimed6/10

   Honeybadger supports rule-like automation: Alarms combine a BadgerQL query with a threshold to trigger alerts automatically (docs-8), anomaly detection triggers alerts when error volume deviates from baseline (docs-9), and deployments automatically resolve open errors and notify teams (docs-6, docs-29). These qualify as user-defined rules triggering automatic actions on events, but there's no evidence of a general-purpose automation/workflow engine (e.g., custom actions beyond alert/resolve/notify) or that AI-native users can programmatically create these rules via API/CLI/MCP. missing for 10: broader custom-action rule engine, API/CLI/MCP support for creating or managing alarms/anomaly rules, independent verification of rule automation working in practice.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

   GlitchTip~partialclaimed4/10

   GlitchTip supports basic event-triggered alerting: new-issue alerts default to emailing team members, but you can add webhook URLs as alert recipients, and uptime monitoring can also fire alerts via email/webhook when a ping fails. This is a simple automatic action-on-event mechanism, but there's no evidence of a broader rule engine (conditions, multi-step workflows, non-alert actions) beyond notify-via-email/webhook. Missing for 10: conditional rule builder, support for triggering arbitrary actions (not just notifications), evidence of chained/automated workflows, and independent confirmation of rule reliability.

   • [claimed-docs] “By default, new project alerts send emails to a project's team members, but you can also add a webhook URL by clicking “Add An Alert Recipie…”
   • [claimed-docs] “GlitchTip can ping your site and warn you when it's not responding. ... If GlitchTip doesn't receive your ping, it will send you an alert vi…”
   • [claimed-docs] “GlitchTip can ping your site and warn you when it's not responding. Or reverse it and send GlitchTip a request on schedule.”

   proof ↗⚑ flag

Pii scrubbing

1. sreScrub PII from error events — server-side scrubbing rules plus SDK-level filtering — before sensitive payloads ever persist

   weight 2 · round drawn
   Honeybadger—none0/10

   No evidence pack items mention PII scrubbing, data filtering, or SDK-level/server-side redaction rules — none of the docs, changelog, or community items reference this capability at all. missing for 10: server-side scrubbing rule configuration, SDK filter_keys/params filtering, any mention of PII/sensitive data handling before persistence.

   ⚑ flag

   GlitchTip—none0/10

   No evidence pack items mention PII scrubbing, server-side scrubbing rules, data-scrubbing configuration, or SDK-level before-send filtering for GlitchTip; the docs cover SDK integration, alerts, CLI, MCP, and performance tracing but never data privacy/scrubbing controls.

   ⚑ flag

Agent access

1. ai-native userAn agent can pull my top production issues with stack traces via API or MCP, triage them, and file the real bugs into my tracker

   weight 3 · round drawn
   Honeybadger~partialprobed6/10

   Honeybadger offers a documented API for fault listing (with stack traces implied via faults/notices) and an official hosted MCP server that lets an AI assistant fetch errors, run BadgerQL queries, and manage projects, which supports pulling and triaging top issues. However, filing bugs into an external tracker is only evidenced via manual GitHub/GitLab/Jira issue export features, not shown as an MCP/agent-driven action, and there's no hands-on/independent proof of the full pull-triage-file workflow via API or MCP. missing for 10: evidence of MCP or API directly creating/filing tickets into external trackers, independent/hands-on confirmation of the end-to-end agent workflow.

   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “your AI assistant can fetch Honeybadger data, analyze patterns, and help investigate production issues within your existing workflow.”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”
   • [probe] “official MCP server documented at https://docs.honeybadger.io/resources/mcp/”

   proof ↗⚑ flag

   GlitchTip~partialprobed6/10

   GlitchTip ships a built-in MCP server that lets AI assistants browse issues, inspect stack traces/event data, and resolve issues, and is documented as Sentry-API-compatible for programmatic access, covering the core 'pull issues with stack traces and triage' portion of the story. However, there's no evidence of a filed-bug/tracker-integration capability (e.g., auto-filing into Jira/GitHub) or of a prioritized 'top production issues' query, and probes show no public OpenAPI spec, weakening independent verification of the API path. Missing for 10: documented ticket-filing/tracker integration from the agent, evidence of 'top issues' ranking via API/MCP, and a public/verifiable API spec.

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [probe] “official MCP server documented at https://glitchtip.com/documentation/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”

   proof ↗⚑ flag

Api access

1. developerList, query, and update issues and fetch raw events through a documented REST API with scoped tokens

   weight 3 · round drawn
   Honeybadger~partialclaimed5/10

   Honeybadger documents a REST API for faults (issues) with list/single-fault retrieval and search-style querying (docs-19, docs-4), plus a reporting API for creating notices, but there is no evidence of an update-issue endpoint, a raw-events fetch endpoint, or explicit scoped-token support (only a generic API key/Honeybadger-Token is mentioned). missing for 10: documented issue-update endpoint, raw event retrieval endpoint, explicit scoped/read-only token documentation.

   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Example query: `john class:UserError -tag:wip -tag:pending component:"UsersController" action:'update'`.”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Requests sent from Honeybadger servers for source maps, web hooks, and uptime checks include the header Honeybadger-Token which is a secret …”

   proof ↗⚑ flag

   GlitchTip~partialprobed5/10

   GlitchTip claims Sentry API compatibility, implying issue listing/query/update and raw event fetch via REST API with tokens, but there is no direct documentation of endpoints, scoping, or token permissions in the evidence, and probes for OpenAPI/API docs all returned 404s. missing for 10: dedicated REST API reference docs, explicit scoped-token/auth documentation, and confirmation of update/query endpoints beyond inferred Sentry compatibility.

   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”

   proof ↗⚑ flag

Ingest protocol

1. developerThe event-ingestion protocol is documented and open enough that custom clients and compatible SDKs can send events without an official SDK

   weight 2 · round to Honeybadger
   Honeybadger✓fullprobed7/10

   Honeybadger documents a plain REST endpoint (POST JSON to https://api.honeybadger.io/v1/notices) for reporting exceptions, plus related endpoints for source maps and deployments, meaning any custom client can integrate without the official SDK. However, there's no formal OpenAPI/schema spec (probe confirms 404s) and no independent evidence of third-party/community SDKs actually built against this raw API. Missing for 10: published OpenAPI/schema definition, independent examples of non-official clients successfully using the ingestion endpoint.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”

   proof ↗⚑ flag

   GlitchTip~partialprobed6/10

   GlitchTip explicitly claims Sentry API compatibility, meaning it reuses Sentry's open-source ingestion protocol/SDK ecosystem rather than a proprietary one, and community reports confirm it works reliably with standard Sentry SDKs including newer ones like Svelte. However, there is no first-party protocol specification, OpenAPI/Swagger schema, or raw DSN/envelope format documentation (probes for openapi.json and docs.md return 404), so a developer building a fully custom client without a Sentry SDK would lack authoritative low-level docs. missing for 10: explicit ingestion protocol/schema docs (envelope format, endpoint spec), OpenAPI/Swagger definition, independent confirmation of custom non-Sentry clients successfully sending events.

   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [community] “I use GlitchTip — it works well! A bit hard to deploy (many moving parts) but that's more a problem with F/OSS Sentry. It's been nice being …”
   • [community] “Hey Glitchtip! Been a happy user for going on a year or so. Super easy to self-host, and because it uses the existing sentry libs it's reall…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”

   proof ↗⚑ flag

Grouping

1. developerThe platform groups thousands of duplicate events into one issue via stack-trace fingerprinting, and I can customize the grouping when it gets it wrong

   weight 3 · round to Honeybadger
   Honeybadger✓fullcommunity8/10

   Docs confirm automatic grouping of identical errors into a single issue with navigation between occurrences, and explicit customization via error class, component, stack trace, or custom fingerprint; community feedback corroborates satisfaction with deduping. Missing for 10: independent/hands-on evidence of the fingerprinting algorithm's accuracy at scale (thousands of events) and real-world examples of re-grouping mistakes being fixed.

   • [claimed-docs] “You can customize the grouping for each exception by changing the error class name, component, or stack trace—or by sending a custom fingerp…”
   • [claimed-docs] “Honeybadger groups identical errors together. Using our navigation bar, you can still navigate between each individual occurrence (or notice…”
   • [community] “Honeybadger so far. Working well enough. Love the deduping.”

   proof ↗⚑ flag

   GlitchTip—none0/10

   The evidence pack covers SDK ingestion, source maps, alerting, CLI, and MCP server features, but never mentions stack-trace fingerprinting, issue grouping of duplicate events, or any custom fingerrule/grouping override capability. The general 'Sentry API compatible' claim (glitchtip-docs-11) does not concretely document grouping behavior or customization tools.

   ⚑ flag

Triage

1. sreTriage issues — assign an owner, resolve, ignore, or snooze — and the platform reopens a resolved issue automatically when it regresses

   weight 3 · round to Honeybadger
   Honeybadger~partialclaimed5/10

   Honeybadger documents resolving and reopening errors (via Slack integration button) and auto-resolving errors on deploy, plus fault listing via API, which covers part of the triage workflow. However, there's no direct evidence of 'assign an owner', 'ignore', or 'snooze' actions, nor confirmation that a resolved issue is automatically reopened when it regresses (only manual reopen via Slack is shown). missing for 10: assign-owner action, ignore action, snooze action, automatic reopening on regression evidence.

   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”

   proof ↗⚑ flag

   GlitchTip~partialclaimed3/10

   Docs confirm issues can be 'resolved' via the MCP interface, and teams route notifications to owners, but there is no evidence of ignore/mute, snooze, explicit assignment workflow, or automatic reopening of a resolved issue upon regression. missing for 10: assign-to-user workflow, ignore/mute action, snooze/time-based silencing, automatic reopen-on-regression behavior.

   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”
   • [claimed-docs] “Teams are for making sure the right people get notified when an error is reported.”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”

   proof ↗⚑ flag

2. developerMerge issues that are really the same bug and split ones the fingerprinter wrongly collapsed

   weight 1 · round to Honeybadger
   Honeybadger~partialclaimed5/10

   Honeybadger documents customizable grouping via custom fingerprints, error class, component, or stack trace, which lets developers effectively split incorrectly-collapsed errors into distinct issues [honeybadger-docs-2][honeybadger-docs-3]. However, there is no documented UI or API action for merging two separately-grouped issues back into one bug — the evidence only covers grouping-at-ingestion via fingerprint customization, not a manual merge workflow. Missing for 10: explicit merge-issues feature/API, evidence of an UI 'merge' action, and independent confirmation that fingerprint changes retroactively re-group existing occurrences.

   • [claimed-docs] “You can customize the grouping for each exception by changing the error class name, component, or stack trace—or by sending a custom fingerp…”
   • [claimed-docs] “Honeybadger groups identical errors together. Using our navigation bar, you can still navigate between each individual occurrence (or notice…”
   • [claimed-docs] “Honeybadger provides powerful search features that let you easily find previously-occurred errors by type, location, meta-data and many othe…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence describes issue merge/unmerge or split functionality for fingerprinting-collapsed groups; the docs mention resolving issues, alerts, and MCP tooling for investigating errors, but nothing about merging or splitting grouped issues.

   ⚑ flag

User feedback

1. developerCollect user feedback — a crash-report dialog or feedback widget — attached to the exact error event the user hit

   weight 1 · round drawn
   Honeybadger—none0/10

   Honeybadger's evidence covers automatic error capture, grouping, search, deployments, and integrations, but there is no mention of a user-facing crash-report dialog or feedback widget that lets end-users submit feedback tied to a specific error occurrence.

   ⚑ flag

   GlitchTip—none0/10

   No evidence of a user feedback widget or crash-report dialog feature attached to error events; documentation covers error/performance tracking, alerts, CLI, and MCP but never mentions collecting end-user feedback tied to an event.

   ⚑ flag

User impact

1. sreEvery issue quantifies real impact — how many users and sessions are affected — so I prioritize by blast radius, not raw event counts

   weight 2 · round drawn
   Honeybadger—none0/10

   Evidence covers error grouping, search, deployments, alarms, and anomaly detection on error volume/rate, but nowhere quantifies user or session impact (e.g., affected-user counts) for prioritization by blast radius. missing for 10: any mention of unique users/sessions affected metric, user-impact scoring, or blast-radius prioritization feature.

   ⚑ flag

   GlitchTip—none0/10

   No evidence GlitchTip surfaces user/session impact metrics (affected users, session counts, or blast-radius prioritization) on issues; docs cover error tracking, performance transactions, alerts, and MCP/CLI tooling but nothing about quantifying user/session impact per issue. Missing for 10: any mention of affected-user counts, session tracking, or blast-radius based prioritization/sorting.

   • [claimed-docs] “GlitchTip can use Sentry's open source SDKs to receive error data from your application.”
   • [claimed-docs] “GlitchTip takes a simple, works out of the box approach. No dashboard building and metrics hunting. Just find your slowest web requests, dat…”
   • [claimed-docs] “Find out where your app is slow. GlitchTip takes a simple, works out of the box approach.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Honeybadger
   Honeybadger~partialprobed5/10

   Honeybadger exposes a documented REST API for core actions—reporting exceptions, deployments, source maps, and listing faults (honeybadger-docs-15,17,19,28)—plus a CLI and MCP server for agent access (honeybadger-docs-18,13,31). However, the probe found no OpenAPI/swagger spec (honeybadger-probe-2), and many UI-only capabilities (resolving/reopening errors, BadgerQL alarm configuration, team/SAML management, account switching) are not shown to have API equivalents. Missing for 10: comprehensive API parity for error resolution, alarms, account/team management, and a published OpenAPI spec confirming full coverage.

   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [claimed-docs] “Once connected, your AI assistant gains the following capabilities: Project management... Error investigation... Insights: Run BadgerQL quer…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.honeybadger.io/openapi.json, https://docs.honeybadger.io/swagger.json, https://docs.hon…”
   • [claimed-docs] “You can create additional accounts and switch between accounts using the dropdown in the navigation bar.”

   proof ↗⚑ flag

   GlitchTip~partialprobed4/10

   GlitchTip claims Sentry API compatibility, implying broad API coverage (glitchtip-docs-11), and separately offers a CLI and MCP server for programmatic/AI access (glitchtip-docs-5, glitchtip-docs-19), but there is no explicit documentation or evidence that every UI action (team/project setup, alerts, uptime monitoring config, etc.) has a corresponding API endpoint, and probes for OpenAPI/API reference docs all 404'd. Missing for 10: a published OpenAPI/API reference confirming full UI-API parity, and explicit documentation or community confirmation that all UI workflows (not just error/issue data) are API-accessible.

   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Honeybadger~partialclaimed3/10

   Honeybadger exposes a REST API (e.g. list/get faults, reporting exceptions) that returns data in JSON, which could be used to script an export of error data, but there is no documented bulk 'export all your account data' feature, no GDPR-style data-portability tool, and no mention of full account deletion/export workflow. missing for 10: dedicated full-account data export feature, documented open-format bulk export tool, evidence of complete data portability/leave workflow.

   • [claimed-docs] “Returns a list of faults or a single fault for the given project”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”

   proof ↗⚑ flag

   GlitchTip~partialprobed3/10

   GlitchTip is self-hosted and 'aims to be Sentry API compatible' (glitchtip-docs-11), implying data stays in the user's own Postgres/Redis stack and could interoperate with other Sentry-compatible tools, but there is no documented explicit 'export all data' feature, bulk export tool, or open-format export (CSV/JSON dump) in the evidence pack, and probes for docs/openapi endpoints returned 404s. Missing for 10: an explicit data-export feature/documentation, evidence of open-format bulk export, and independent confirmation that self-hosting alone satisfies full data portability.

   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [community] “GlitchTip only requires 4 components (backend, workers, Redis, and postgresql). Self Hosted Sentry requires many more (at least a dozen, inc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://glitchtip.com/openapi.json, https://glitchtip.com/swagger.json, https://glitchtip.com/api/op…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Honeybadger—none0/10

   Honeybadger is a closed, commercial SaaS product; no evidence in the pack indicates its source code is published under an open license (client libraries being open-source is not addressed, and the core service is proprietary). Missing for 10: any mention of an open-source license, public source repository, or licensing terms.

   ⚑ flag

   GlitchTip—none0/10

   The evidence pack never mentions GlitchTip's own source code license or a public repository — the only 'open source' references are to Sentry's SDKs, not to GlitchTip's own codebase. Since the axis (whether an AI-native user can read the product's source under an open license) plainly applies to a self-hostable product like this, absence of evidence means 'none'.

   • [claimed-docs] “GlitchTip can use Sentry's open source SDKs to receive error data from your application.”
   • [claimed-docs] “GlitchTip can be run with Docker. We recommend Docker Compose, PikaPods, Elestio, Nodion, Railway, or RepoCloud.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to GlitchTip
   Honeybadger—none0/10

   Honeybadger is presented as a hosted SaaS product (api.honeybadger.io) with no evidence of an open-source self-hosted core, on-premise deployment option, or Docker/self-host installation guide anywhere in the evidence pack.

   ⚑ flag

   GlitchTip✓fullcommunity8/10

   GlitchTip documents self-hosting via Docker/Docker Compose with multiple hosting recommendations (PikaPods, Elestio, Railway, etc.), and community reports corroborate this is a real, working, relatively lightweight self-hosting path (only 4 components vs Sentry's dozen) with good stability in practice. Missing for 10: no first-party hardware/scaling guidance beyond basic install docs, and one community comment notes deployment complexity ('many moving parts').

   • [claimed-docs] “GlitchTip can be run with Docker. We recommend Docker Compose, PikaPods, Elestio, Nodion, Railway, or RepoCloud.”
   • [community] “I use GlitchTip — it works well! A bit hard to deploy (many moving parts) but that's more a problem with F/OSS Sentry. It's been nice being …”
   • [community] “GlitchTip only requires 4 components (backend, workers, Redis, and postgresql). Self Hosted Sentry requires many more (at least a dozen, inc…”
   • [community] “Stability on GlitchTip has been great for me -- haven't had to worry about it or babysit it too much. Very small scale but still quite promi…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to GlitchTip
   Honeybadger—none0/10

   No evidence in the pack addresses data residency, regional hosting options, or ability to choose where data is stored; only data retention (Insights replication) and security token handling are mentioned. missing for 10: any mention of region selection, EU/US hosting options, or data residency controls.

   ⚑ flag

   GlitchTip~partialclaimed6/10

   GlitchTip explicitly offers a data residency option (a fully independent EU instance hosted in Frankfurt) plus self-hosting via Docker, which lets users control where data lives; a BAA is also available for compliance needs. However, evidence does not show a broader multi-region choice (e.g., US/EU/APAC selection at signup) beyond the single EU instance and self-hosting. Missing for 10: documented region selection UI/API, list of supported regions beyond EU, and independent confirmation of residency guarantees.

   • [claimed-docs] “For organizations with data residency requirements, GlitchTip offers a fully independent EU instance hosted in Frankfurt, Germany”
   • [claimed-docs] “Business Associate Agreement (BAA) available upon request”
   • [claimed-docs] “GlitchTip can be run with Docker. We recommend Docker Compose, PikaPods, Elestio, Nodion, Railway, or RepoCloud.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to GlitchTip
   Honeybadger—none0/10

   No evidence in the pack addresses AI training data usage or opt-out policies for Honeybadger's data; the product is an error-tracking/monitoring tool and this axis is plausible (e.g., a privacy policy statement about AI training) but nothing documents it. Missing for 10: any privacy policy statement on AI training data usage, opt-out mechanism, or data processing terms addressing AI model training.

   ⚑ flag

   GlitchTip~partialclaimed5/10

   GlitchTip's self-hosting option and EU data residency (Frankfurt) give users control over where data lives, and its MCP server explicitly markets 'no data sharing required' for AI tool integration, implying data stays local. However, there is no explicit policy or documentation addressing AI model training use of customer/error data specifically, no opt-out toggle, or terms language on this topic. missing for 10: explicit AI-training data-use policy/opt-out, terms of service language on model training, independent confirmation of no training use.

   • [claimed-docs] “GlitchTip has a built-in MCP server so you can pull your own error data into your preferred AI tools with no data sharing required.”
   • [claimed-docs] “GlitchTip includes a built-in MCP server that allows AI assistants to interact with your error tracking, performance, and log data.”
   • [claimed-docs] “For organizations with data residency requirements, GlitchTip offers a fully independent EU instance hosted in Frankfurt, Germany”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Honeybadger—none0/10

   Evidence only hints that Business/Enterprise accounts can replicate Insights data for longer retention (docs-22), but there is no mention of any user-facing control to configure retention windows, purge/delete data on demand, or comply with deletion requests. Missing for 10: documented retention settings, a data-deletion API/UI, and any GDPR-style erasure mechanism.

   • [claimed-docs] “If you need to keep your Insights data longer than Honeybadger stores it, Business and Enterprise accounts can now replicate”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence pack items address data retention policies, configurable retention windows, or user-initiated deletion of stored error/event data; self-hosting and EU residency are mentioned but retention/deletion controls are never described.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Honeybadger—none0/10

   Honeybadger itself is an error-tracking/telemetry product whose core function is collecting data from customer apps; the evidence pack contains no mention of an opt-out mechanism for telemetry/usage tracking related to the AI assistant/MCP integration or the product's own data collection practices. Since this axis (opting out of tracking) is a fair privacy-posture question for an AI-native user of any product, but no evidence shows such an opt-out exists, the verdict is none. Missing for 10: any documentation of an opt-out/telemetry-disable setting, privacy controls for AI assistant usage data, or opt-out options for the MCP integration.

   ⚑ flag

   GlitchTip—none0/10

   GlitchTip is a self-hosted error-tracking tool; being self-hosted implies the operator controls their own data, but no evidence explicitly addresses a telemetry/usage-tracking opt-out setting for GlitchTip itself (e.g., anonymous usage stats sent to the vendor). The MCP server 'no data sharing' claim relates to AI tool data flow, not product telemetry opt-out.

   ⚑ flag

Quotas

1. engineering leaderCap event quotas per project and set spend limits so an error storm burns a predictable budget, never a surprise invoice

   weight 2 · round drawn
   Honeybadger—none0/10

   No evidence anywhere in the pack of event quota caps, spend/budget limits, or usage-based throttling controls for a project; the evidence covers error grouping, search, deployments, alarms, and MCP/CLI integrations but nothing about cost or quota governance.

   ⚑ flag

   GlitchTip—none0/10

   The evidence pack shows only trace sampling rate configuration (tracesSampleRate) as a way to reduce volume, but nothing about per-project event quotas, spend limit caps, or billing alerts to prevent surprise invoices. Given GlitchTip is a hosted/paid product with pricing plans, this axis applies, but no documentation or community evidence confirms a quota/spend-cap feature.

   • [claimed-docs] “This rate can be set with the `tracesSampleRate` config option ... Set this to a low number like `0.01` to have your SDK send only 1 percent…”
   • [claimed-docs] “Business Associate Agreement (BAA) available upon request”

   proof ↗⚑ flag

Regressions

1. sreI get alerted when an error that was fixed comes back in a newer release, distinct from ordinary new-issue noise

   weight 2 · round to Honeybadger
   Honeybadger~partialclaimed5/10

   Honeybadger auto-resolves errors on deploy and tracks reoccurrences (doc-6, doc-29), and Slack messages include a 'resolve or reopen' button implying errors can reopen (doc-10), which is the mechanical basis for detecting a fixed error's return. However, there is no explicit evidence of a distinct 'regression' alert type or notification that flags a reopened error differently from a brand-new issue, so SREs would have to infer regressions from reopen state rather than get a dedicated alert. Missing for 10: explicit regression-specific alert/notification distinct from new-issue alerts, and confirmation that reopening a resolved error triggers a notification at all.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”

   proof ↗⚑ flag

   GlitchTip—none0/10

   Evidence shows GlitchTip supports release tracking (glitchtip-cli releases/deploys) and generic alerting on new issues via email/webhook, but there is no mention of a distinct 'regression' alert type that fires specifically when a previously resolved issue reappears in a newer release, as opposed to ordinary new-issue notifications.

   • [claimed-docs] “By default, new project alerts send emails to a project's team members, but you can also add a webhook URL by clicking “Add An Alert Recipie…”
   • [claimed-docs] “Record deployments for a release: glitchtip-cli deploys new 1.0.0 --env production --org my-org --project my-project”
   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”

   proof ↗⚑ flag

Release health

1. sreWatch release health — crash-free sessions and users, adoption per release — and compare a canary release against the last stable one

   weight 2 · round drawn
   Honeybadger—none0/10

   Honeybadger documents deployment tracking (correlating errors with deploys, diffing against last deploy, auto-resolving errors on deploy) but there is no evidence of crash-free sessions/users metrics or per-release adoption percentages, which are the specific release-health metrics this story asks about.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “When GitHub or GitLab is connected, Honeybadger links the revision to a comparison page that shows a diff of what changed since the last dep…”
   • [claimed-docs] “Use this endpoint to notify Honeybadger when a deploy occurs.”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   GlitchTip has releases/deployments tracking via CLI and basic performance monitoring, but there is no evidence of release health metrics like crash-free sessions/users, adoption rate per release, or canary vs stable comparison dashboards.

   ⚑ flag

Release tracking

1. developerAssociate errors with releases and commits so each issue shows the release it first appeared in and the suspect commit that likely caused it

   weight 3 · round to Honeybadger
   Honeybadger~partialclaimed5/10

   Honeybadger's deployment tracking records deploys, auto-resolves errors on deploy, and (with GitHub/GitLab connected) links a revision to a diff of what changed since the last deploy, plus supports queries like 'occurred.after:last deploy' to correlate errors with releases. However, there's no documented evidence of a per-issue 'first seen in release X' badge or automatic 'suspect commit' attribution pinpointing which commit likely caused a specific error, which is the core of this story. Missing for 10: explicit per-error 'first appeared in release' metadata, automated suspect-commit/blame attribution shown on the issue itself, independent corroboration of this workflow.

   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “When GitHub or GitLab is connected, Honeybadger links the revision to a comparison page that shows a diff of what changed since the last dep…”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”

   proof ↗⚑ flag

   GlitchTip~partialclaimed4/10

   GlitchTip's CLI documents creating releases and recording deployments (glitchtip-cli releases new / deploys new), which lets teams tag error events with release versions, but there is no evidence of associating commits with issues or surfacing a 'suspect commit' on an issue as Sentry does. missing for 10: commit/VCS integration for suspect-commit detection, evidence that issue pages display 'first seen in release' or commit blame, independent confirmation of this workflow.

   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”
   • [claimed-docs] “Record deployments for a release: glitchtip-cli deploys new 1.0.0 --env production --org my-org --project my-project”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”

   proof ↗⚑ flag

Event context

1. developerAttach breadcrumbs, custom tags, and user context to every event so a stack trace arrives with the state that produced it

   weight 2 · round to GlitchTip
   Honeybadger~partialclaimed4/10

   Evidence shows tag-based search syntax (implying tags can be attached) and a changelog note about 'event context' and 'event correlation' configuration in JS packages, but there is no explicit documentation of breadcrumb trails or explicit user-context attachment on error notices. missing for 10: explicit breadcrumb API/docs, explicit user context attachment API, worked example showing tags+context+breadcrumbs together on a single event.

   • [claimed-docs] “Example query: `john class:UserError -tag:wip -tag:pending component:"UsersController" action:'update'`.”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”
   • [claimed-docs] “You can customize the grouping for each exception by changing the error class name, component, or stack trace—or by sending a custom fingerp…”

   proof ↗⚑ flag

   GlitchTip~partialcommunity6/10

   GlitchTip relies on Sentry's official SDKs for event capture and explicitly claims Sentry API compatibility ('Anything that works with Sentry should also work with GlitchTip'), which implies inherited support for breadcrumbs, tags, and user context since these are core Sentry SDK features. However, the evidence pack never explicitly documents these specific instrumentation primitives (breadcrumbs, tag API, user context) on GlitchTip's own docs. Missing for 10: explicit GlitchTip documentation demonstrating breadcrumb capture, custom tag attachment, and user context APIs, plus hands-on confirmation these render correctly in the GlitchTip UI.

   • [claimed-docs] “GlitchTip can use Sentry's open source SDKs to receive error data from your application.”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [community] “I use GlitchTip — it works well! A bit hard to deploy (many moving parts) but that's more a problem with F/OSS Sentry. It's been nice being …”
   • [community] “Hey Glitchtip! Been a happy user for going on a year or so. Super easy to self-host, and because it uses the existing sentry libs it's reall…”

   proof ↗⚑ flag

Mobile crashes

1. developerCapture native mobile crashes — iOS, Android, NDK — with the device, OS, and app-version context needed to reproduce them

   weight 2 · round to GlitchTip
   Honeybadger—none0/10

   Evidence pack covers Ruby, JS, and general error-reporting APIs, deployments, integrations, and MCP/CLI tooling, but contains no mention of iOS, Android, or NDK SDKs, or native mobile crash context (device, OS, app version). Missing for 10: iOS SDK docs, Android SDK docs, NDK/native crash capture, mobile device/app-version context capture.

   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”

   proof ↗⚑ flag

   GlitchTip~partialclaimed4/10

   GlitchTip relies on Sentry's open-source SDKs (which include official iOS/Android/NDK SDKs) and its CLI explicitly supports uploading debug symbols for native apps (dSYM, PDB, ELF) for crash symbolication, implying native mobile crash capture is possible. However, there is no explicit documentation of the mobile SDK setup, device/OS/app-version context capture, or any hands-on confirmation of iOS/Android/NDK crash reporting working end-to-end. Missing for 10: explicit iOS/Android SDK integration docs, device/OS/app-version context field documentation, and independent verification of native crash reproduction.

   • [claimed-docs] “GlitchTip can use Sentry's open source SDKs to receive error data from your application.”
   • [claimed-docs] “Upload debug symbols for native applications (dSYM, PDB, ELF): glitchtip-cli debug-files upload ./build --org my-org --project my-project”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”

   proof ↗⚑ flag

Sdk coverage

1. developerInstrument my web frontend, backend services, and mobile apps with official SDKs that capture uncaught errors automatically

   weight 3 · round to GlitchTip
   Honeybadger~partialclaimed6/10

   Docs confirm automatic uncaught-error capture via client libraries ("errors thrown by your application are automatically sent to our API"), JS/frontend automatic instrumentation and source-map support, and a generic exceptions API for backend reporting. However, the evidence pack lacks explicit confirmation of dedicated mobile SDKs (iOS/Android) or a list of officially supported backend languages beyond the Ruby CLI/gem reference, so mobile coverage is unconfirmed. Missing for 10: explicit mobile SDK documentation, multi-language backend SDK list, independent hands-on verification of auto-capture across platforms.

   • [claimed-docs] “Once our client library is installed and configured, errors thrown by your application are automatically sent to our API.”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”
   • [claimed-docs] “Capture HTTP requests with automatic instrumentation and take advantage of new configuration options for event correlation, event context, h…”
   • [claimed-docs] “Report errors using our [exceptions API](/api/reporting-exceptions/)”
   • [claimed-docs] “Your JSON payload should be submitted as the body of a POST request to https://api.honeybadger.io/v1/notices”

   proof ↗⚑ flag

   GlitchTip✓fullcommunity7/10

   GlitchTip explicitly documents using Sentry's open-source SDKs for error capture and claims Sentry API compatibility, meaning any Sentry SDK (web, backend, mobile) works out of the box; community reports confirm reliable use of the Sentry SDK ecosystem across frameworks like Svelte. missing for 10: explicit mention of mobile SDK support/testing, and no independent hands-on confirmation of automatic uncaught-error capture across all three platform types (frontend/backend/mobile).

   • [claimed-docs] “GlitchTip can use Sentry's open source SDKs to receive error data from your application.”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [community] “I use GlitchTip — it works well! A bit hard to deploy (many moving parts) but that's more a problem with F/OSS Sentry. It's been nice being …”
   • [community] “Hey Glitchtip! Been a happy user for going on a year or so. Super easy to self-host, and because it uses the existing sentry libs it's reall…”

   proof ↗⚑ flag

Dashboards

1. engineering leaderSee error trends across projects and teams on dashboards — top regressions, new issues per release, volume over time

   weight 2 · round to Honeybadger
   Honeybadger~partialclaimed6/10

   Honeybadger's BadgerQL/Insights, deployment tracking (correlating errors with releases, 'occurred.after:last deploy' queries), and anomaly detection support volume-over-time and per-release regression tracking, giving engineering leaders solid analytics tools. However, evidence never shows a native cross-project/cross-team rollup dashboard — only per-account switching (docs-34) — so the 'across projects and teams' aggregation aspect of the story is unproven. Missing for 10: explicit cross-project/team aggregated dashboard UI, named 'top regressions' report, and independent/hands-on confirmation of dashboard usability at leadership level.

   • [claimed-docs] “Alarms combine a BadgerQL query (“count all slow requests in the past five minutes”) with a threshold (“when count is > 2”) and trigger aler…”
   • [claimed-docs] “Anomaly detection alerts you when a project’s total error volume deviates from its learned baseline... notifies you when the current rate is…”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Deployment tracking lets you record when your app is deployed, see a history of deployments, and correlate code changes with errors. When yo…”
   • [claimed-docs] “Honeybadger provides powerful search features that let you easily find previously-occurred errors by type, location, meta-data and many othe…”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”
   • [claimed-docs] “You can create additional accounts and switch between accounts using the dropdown in the navigation bar.”

   proof ↗⚑ flag

   GlitchTip—none0/10

   Evidence covers issue creation, teams/projects, CLI-based release tracking, and an MCP server for browsing individual errors, but there is no mention of cross-project/team dashboards, top-regression views, new-issues-per-release rollups, or volume-over-time charts. In fact one doc explicitly states GlitchTip avoids 'dashboard building and metrics hunting,' suggesting this kind of leadership-level trend dashboard is not a focus. missing for 10: cross-project/team aggregate dashboards, top-regression identification, new-issues-per-release reporting, volume-over-time visualizations.

   • [claimed-docs] “GlitchTip takes a simple, works out of the box approach. No dashboard building and metrics hunting. Just find your slowest web requests, dat…”
   • [claimed-docs] “Teams are for making sure the right people get notified when an error is reported.”
   • [claimed-docs] “Investigate errors — Browse issues, inspect stack traces and event data, and resolve issues”
   • [claimed-docs] “Record deployments for a release: glitchtip-cli deploys new 1.0.0 --env production --org my-org --project my-project”
   • [community] “Clicking any of the blog posts takes me to the installation guide. I can't seem to find any feature overview? I'd like to see screenshots an…”

   proof ↗⚑ flag

Event search

1. developerSearch and filter events across projects by tag, release, environment, and custom properties with a real query syntax

   weight 2 · round to Honeybadger
   Honeybadger✓fullclaimed8/10

   Honeybadger documents a real BadgerQL-style query syntax (tag:, class:, component:, action:, occurred.after: 'last deploy', negation with -tag:) for filtering errors/events by tag, release/deploy, environment-like properties and custom fields, plus a natural-language-to-query assist feature and Insights query capabilities for aggregation/filtering across fields. missing for 10: explicit documentation of cross-project search/filtering (queries appear scoped per-project) and independent hands-on validation of the query syntax's breadth beyond docs.

   • [claimed-docs] “Example query: `john class:UserError -tag:wip -tag:pending component:"UsersController" action:'update'`.”
   • [claimed-docs] “You can search for errors without writing the query yourself. Click the lightbulb icon next to the search box to open the “Describe your sea…”
   • [claimed-docs] “`occurred.after:'last deploy'` Errors that occurred since the most recent deployment”
   • [claimed-docs] “Honeybadger provides powerful search features that let you easily find previously-occurred errors by type, location, meta-data and many othe…”
   • [claimed-docs] “Honeybadger's error search and BadgerQL can answer almost any question about your e”
   • [claimed-docs] “With it you can specify which fields you want to see, filter the kinds of events that should be returned, perform aggregations and calculati…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence describes a search/query syntax for filtering events by tag, release, environment, or custom properties; documentation covers SDK integration, alerts, CLI releases, MCP server, and performance monitoring but not a query/search feature across projects.

   ⚑ flag

Sourcemaps

1. developerUpload JavaScript source maps from CI — via CLI or bundler plugin — so production stack traces show my original source, not minified frames

   weight 3 · round drawn
   Honeybadger~partialprobed6/10

   Honeybadger documents a Source Map Upload API for un-minifying JS stack traces (honeybadger-docs-16, honeybadger-docs-28), and it has a general CLI (honeybadger-docs-18, honeybadger-probe-4) with deploy notification support, but the evidence never explicitly shows a CI-oriented source map upload command in that CLI or a bundler plugin (webpack/rollup/vite) for automated CI upload. missing for 10: explicit CLI subcommand or bundler plugin for source map upload, CI usage examples/integration guide, independent confirmation of correct symbolication in production.

   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”
   • [claimed-docs] “The Honeybadger CLI provides a Command Line Interface for various Honeybadger-related programs and utilities.”
   • [probe] “official CLI documented at https://docs.honeybadger.io/lib/ruby/gem-reference/cli/”

   proof ↗⚑ flag

   GlitchTip~partialprobed6/10

   GlitchTip explicitly documents uploading source maps via its CLI (Beta) with debug ID injection for readable JS stack traces, and the CLI supports release/deploy tracking consistent with CI workflows. However, evidence for a dedicated bundler plugin (webpack/vite/rollup) is absent, the CLI feature is marked Beta, and there's no independent/community confirmation of source map upload working in practice. Missing for 10: bundler plugin support, CI pipeline examples, hands-on/community verification of accurate deminification.

   • [claimed-docs] “For JavaScript projects, upload source maps to get readable stack traces. Use the GlitchTip CLI (Beta) to inject debug IDs and upload source…”
   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”
   • [claimed-docs] “Record deployments for a release: glitchtip-cli deploys new 1.0.0 --env production --org my-org --project my-project”
   • [probe] “official CLI documented at https://glitchtip.com/documentation/cli”

   proof ↗⚑ flag

Symbolication

1. developerUpload dSYM, ProGuard, and native debug symbols so mobile and native crashes symbolicate to real function names and lines

   weight 2 · round to GlitchTip
   Honeybadger—none0/10

   Evidence shows Honeybadger supports JavaScript source map upload/unminification (docs-16, docs-28) but contains no mention of dSYM, ProGuard, or native mobile debug symbol upload/symbolication anywhere in the pack.

   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files. Use the Source Map …”
   • [claimed-docs] “Honeybadger can automatically un-minify your JavaScript code if you provide a source map along with your minified files.”

   proof ↗⚑ flag

   GlitchTip~partialclaimed6/10

   GlitchTip's CLI explicitly supports uploading native debug symbols (dSYM, PDB, ELF) via `glitchtip-cli debug-files upload`, directly addressing native/mobile symbolication, and its Sentry-SDK compatibility implies ProGuard mapping support could work similarly to Sentry. However, there is no explicit documentation or community confirmation of ProGuard mapping upload or Android/Java symbolication specifically, and no hands-on evidence of successful symbolication for mobile crashes. Missing for 10: explicit ProGuard/Android mapping upload docs, independent confirmation of successful mobile crash symbolication.

   • [claimed-docs] “Upload debug symbols for native applications (dSYM, PDB, ELF): glitchtip-cli debug-files upload ./build --org my-org --project my-project”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [claimed-docs] “glitchtip-cli releases new 1.0.0 --org my-org --project my-project”

   proof ↗⚑ flag

Issue trackers

1. developerLink an error to Jira, GitHub Issues, or Linear with two-way status sync, so fixing the ticket resolves the error and a regression reopens it

   weight 2 · round to Honeybadger
   Honeybadger~partialclaimed4/10

   Honeybadger documents issue export/linking to GitHub, GitLab, and Jira (including full Jira wiki markup), and auto-resolves errors on deploy, but there is no evidence of Linear integration nor explicit two-way status sync where resolving/reopening the external ticket automatically resolves/reopens the Honeybadger error (only Slack shows resolve/reopen buttons within Honeybadger itself). missing for 10: Linear integration, documented two-way sync (ticket resolution reopening/closing the Honeybadger error automatically), independent confirmation of sync behavior.

   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”
   • [claimed-docs] “By default, all unresolved errors are automatically marked as resolved when a deployment is recorded, which helps keep your error list clean…”
   • [claimed-docs] “Messages about errors include a button to resolve or reopen the error”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence of Jira/GitHub Issues/Linear integrations with two-way status sync; GlitchTip's documented integrations cover GitLab error tracking, Grafana data source, and an MCP server, none of which mention issue tracker linking or bidirectional resolve/reopen sync.

   • [claimed-docs] “In GitLab, navigate to a project's Settings > Monitor > Error Tracking. Click to enable tracking. Select "Sentry" and enter the GlitchTip UR…”
   • [claimed-docs] “In Grafana, navigate to Configuration > Data sources, click "Add data source". In the search field, type "Sentry".”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”

   proof ↗⚑ flag

Scm context

1. developerThe platform connects to my repos so an issue shows suspect commits and code owners, and I can jump from a stack frame to the exact line on my default branch

   weight 2 · round drawn
   Honeybadger—none0/10

   Evidence shows Honeybadger connects to GitHub/GitLab for deploy diffs and issue exports (docs-7, docs-23), but there is no evidence of suspect-commit identification, code-owner attribution, or jumping from a stack frame to the exact line on the default branch in the repo. Missing for 10: suspect commit detection, code owner mapping, stack-frame-to-source-line deep linking.

   • [claimed-docs] “When GitHub or GitLab is connected, Honeybadger links the revision to a comparison page that shows a diff of what changed since the last dep…”
   • [claimed-docs] “We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full ma…”

   proof ↗⚑ flag

   GlitchTip—none0/10

   No evidence of repo/VCS integration (suspect commits, code owners, or stack-frame-to-source-line linking to a default branch); evidence covers source maps for readable stack traces, GitLab error tracking setup, and an MCP server for AI tools, none of which describe commit suspicion, code ownership, or jump-to-line-on-branch features.

   • [claimed-docs] “For JavaScript projects, upload source maps to get readable stack traces. Use the GlitchTip CLI (Beta) to inject debug IDs and upload source…”
   • [claimed-docs] “GlitchTip aims to be Sentry API compatible. Anything that works with Sentry should also work with GlitchTip.”
   • [claimed-docs] “In GitLab, navigate to a project's Settings > Monitor > Error Tracking. Click to enable tracking. Select "Sentry" and enter the GlitchTip UR…”

   proof ↗⚑ flag