Errora documentation
Errora (ارورا) is an alternative to Sentry: error monitoring, tracing, structured logs, session replay, cron and uptime monitoring, user feedback, profiling, application metrics, dashboards — plus an MCP server and AI auto-fix that opens merge requests for you.
Errora is Sentry-wire-compatible. You instrument your app with the official Sentry SDK for your platform and point its DSN at Errora. There is no Errora-specific client library to install, and no vendor lock-in: the same code sends to Sentry or Errora depending on one environment variable.
Start here
Quickstart →
Create an organization and project, grab your DSN, and see your first error in five minutes.
Core concepts →
Organizations, projects, DSN keys, events, issues, traces, environments and releases.
SDK setup →
JavaScript, Node.js, Python, PHP/Laravel, Go and every other Sentry platform.
Product tour →
The in-app guided tour of the dashboard — and how to replay it whenever you want.
Products
Every feature below has its own setup guide — what to enable in the SDK, what to configure in the UI, and how to verify data is arriving.
| Product | What it gives you |
|---|---|
| Error monitoring | Grouped exceptions, stack traces, trends, assignment, workflow |
| Performance & tracing | Transactions, spans, waterfalls, throughput and latency |
| Structured logs | Severity levels, typed attributes, trace correlation, full-text search |
| Session replay | rrweb recordings of the sessions that produced an error |
| User feedback | The widget, the crash-report modal and the server-side report API |
| Cron monitoring | Check-ins against a crontab/interval schedule, missed & timed-out jobs |
| Uptime monitoring | Scheduled HTTP checks with assertions and downtime issues |
| Profiling | Sampled stack profiles, flamegraphs and slowest-function rankings |
| Metrics | Counters, distributions, gauges and sets over trace_metric or statsd |
| Dashboards | Custom charts, tables and big numbers across every dataset |
| AI monitoring (Insights) | gen_ai.* / mcp.* spans → agent runs, token usage, tool calls |
| Security policy reports | CSP / Expect-CT / HPKP report-uri endpoint |
| Source maps & releases | Upload artifacts, symbolicate minified JavaScript frames |
| AI auto-fix | Draft a patch from a stack trace and open a merge request |
| Alerts & notifications | Webhook, Mattermost, Telegram, Bale, Email, SMS |
| Integrations | GitLab/GitHub repositories and external issue tracking |
| MCP server | Let Claude, Cursor and friends query and triage your issues |
How Errora fits together
Your app ──(official Sentry SDK, your DSN)──▶ Errora
│
┌─────────────────┬───────────────┼───────────────┬──────────────────┐
▼ ▼ ▼ ▼ ▼
Issues (grouped Performance, Logs, metrics, Cron & uptime Alerts → Telegram,
exceptions) profiles, replays, monitors Bale, email, SMS,
AI monitoring user feedback Mattermost, webhook
Your app sends; Errora accepts the payload immediately and does the grouping and storage on its own time, so instrumentation never adds latency to your requests.
Getting help
- API reference — REST API, ingestion endpoints; the live
OpenAPI schema is at
/api/schema/and Swagger UI at/api/docs/on your Errora backend. - Account & organization — organizations and roles, projects and DSN keys, access tokens.
- Billing — wallet and pay-as-you-go pricing.