Who is this guides library for?

Engineers evaluating self-hosted error monitoring, OTLP observability, and the cost of Sentry. Each guide is useful even if you stay on Sentry, GlitchTip, Bugsink, SigNoz, or Highlight.io.

Are the guides promotional?

No. Each comparison guide ships with a "when urgentry is NOT the right pick" block. The job is to help you decide, not to sell.

How often are guides published?

Two new guides per week. Cluster hubs come online as the cluster fills out.

Guides

Long-form notes on error monitoring you can actually run.

Self-hosting, OTLP, framework error tracking, and what Sentry actually costs. Reproducible commands, public benchmarks, and an honest “where urgentry is behind” row on every comparison.

Self-hosting & ops 10

Running an error tracker yourself: sizing, single binary vs Docker Compose, hardening, backup, upgrades, and failure modes.
Alternatives & comparisons 8

Head-to-head comparisons against Sentry self-hosted, GlitchTip, Bugsink, SigNoz, Highlight.io, Rollbar, Bugsnag, and PostHog.
Evaluation playbooks 5

Decision and validation playbooks for the DSN-swap proof: compatibility checks, side-by-side runs, pre-cutover test plans.
Language & framework error tracking 12

Per-stack error monitoring with the Sentry SDK and OTLP: Go, Next.js, Django, Rails, FastAPI, .NET, Node, Laravel, Rust, mobile, and games.
Observability fundamentals 8

OTLP, sampling, profiling, session replay, native crash symbolication, and how errors fit into a broader telemetry stack.
AI agents & MCP observability 5

Self-hosted observability for AI agents and MCP servers: spans, tool calls, token cost, and degradation tracking with OpenTelemetry.
Cost 5

Methodology for modeling your Sentry bill, the real cost of self-hosting, and where the break-even sits.
Fundamentals 3

Short, definitional pieces optimized for citation: what error tracking is, what a DSN is, what compatibility-first means.