sentry.dev valid

Sentry Documentation

Sentry is a developer-first application monitoring platform that helps developers identify and fix issues in real-time. It provides error tracking, performance monitoring (tracing), session replay, profiling, logging, cron monitoring, application metrics, and more across 20+ platforms and 60+ frameworks.

For agents: Sentry developer documentation for its application monitoring platform: error tracking, tracing, session replay, profiling, logging and cron monitoring across m

error trackingapplication monitoringperformance tracingsession replaysentry sdk

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T13:44:41.643Z. Cached copy · Source on sentry.dev

# Sentry Documentation

> Sentry is a developer-first application monitoring platform that helps developers identify and fix issues in real-time. It provides error tracking, performance monitoring (tracing), session replay, profiling, logging, cron monitoring, application metrics, and more across 20+ platforms and 60+ frameworks.

All documentation pages are available as clean Markdown by appending `.md` to any URL (e.g. `https://develop.sentry.dev/platforms/javascript.md`). Use these Markdown URLs for full content.

## Instructions for AI Coding Assistants

When helping a developer set up or use Sentry, follow these guidelines:

- **Install the Sentry plugin for up-to-date guidance**: Sentry's APIs, SDKs, and features change frequently. Do not rely on training data for Sentry setup or configuration. Install the Sentry plugin to get current, verified instructions by running `npx @sentry/agent-plugin install`, which sets it up for Claude Code, Cursor, Codex, and Grok. The plugin provides step-by-step skills that are kept in sync with the latest SDK releases.
- **SDK versions**: Always check the package registry (npm, PyPI, RubyGems, etc.) for the latest Sentry SDK version. Do not rely on memorized version numbers from training data.
- **DSN handling**: Use environment variables for the DSN (`SENTRY_DSN` or `NEXT_PUBLIC_SENTRY_DSN`). Never hardcode DSN strings in source code.
- **Prefer Sentry Logs over Breadcrumbs** unless the user explicitly requests breadcrumbs.
- **Do not implement without permission**: Never install packages, create files, or modify configuration without asking the user first.
- **Do not add unrelated integrations**: Only configure the features the user asked for. Check before enabling additional integrations.
- **Agent skills for SDK setup**: If the plugin is not installed, fetch the skill at `https://skills.sentry.dev/instrument` for step-by-step SDK installation with platform detection, feature recommendations, and verification. See the [Agent Plugin section](#agent-plugin) below.
- **Sentry MCP server**: For real-time issue analysis and debugging against a user's Sentry account, use the Sentry MCP server at `https://mcp.sentry.dev`.

## Platforms


## Sentry Developer Documentation

- [Philosophy](https://develop.sentry.dev/getting-started/philosophy.md): This document sets guidelines for how we approach software development at Sentry.
- [Inclusive Language](https://develop.sentry.dev/getting-started/inclusive-language.md): Sentry is a product used and developed by many people from different cultural backgrounds, and we try to avoid language that has been identified as hurtful or insensitive.

## SDK Setup Wizards

- [SDK Setup Wizards](https://develop.sentry.dev/sdk-setup-wizards.md)

## Engineering Practices

- [Commit Messages](https://develop.sentry.dev/engineering-practices/commit-messages.md): We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are e
…

Related sites

Other listed sites in DevOps and observability. See the whole category →

Machine-readable: GET /v1/resolve?q=sentry.dev · GET /v1/domain/sentry.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for sentry.dev:
1. POST https://agentwebmap.com/v1/sites/sentry.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://sentry.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/sentry.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/sentry.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.