Error Dashboard

The AbrovaTrace error dashboard is the Trace → Issues page in Abrova Console. It shows grouped errors from every platform of your project, with powerful filtering, status management, and detailed error context.

Dashboard Components#

Status Tabs

Each status tab shows how many issues it holds:

Filters

• Status: Open (default), In progress, Resolved, Ignored, Archived, All
• Frequency: 1–10, 11–50, 51–100, 100+ events
• Time Range: 1 hour, 24 hours, 7 days, 30 days (default), or a custom range
• Platform, Environment, Release

Error List

Each issue in the list shows its platform, error message, status, event count and when it was last seen. Switch between the list and timeline views.

Error Detail View#

Click any error to see its full details:

• Error Message & Stack Trace — Full stack trace (deobfuscated when source maps or dSYMs are uploaded)
• Breadcrumbs Timeline — Sequence of events leading to the error
• Extra Context Data — Custom data attached via the extra parameter
• Environment Information — Platform, OS, browser, release version
• Occurrence Statistics — First seen, last seen, total count, and status history

Status Management#

Bulk Updates: Select multiple issues to resolve, mark in progress, ignore, archive or reopen them at once, or resolve every open issue from the ⋯ menu. Changing status needs the member role or higher; deleting issues needs admin or owner — see Roles & Permissions.

Roles & Permissions#

What you can do in Abrova Trace depends on your role. Roles are given in Abrova Console (organisation and project settings); Abrova Trace has no separate role list. Each role includes everything of the one above it.

• You only see your projects. Members and viewers see the projects they are assigned to; other projects of the organisation do not appear in Abrova Trace for them.
• Added to one project only? Someone added to a single project without a role in the organisation is read-only there, like a viewer.
• Refused actions. Controls you cannot use are shown disabled. If a request needs a higher role, the API answers 403 with "code": "forbidden_role".
• Apps and servers are separate. Roles apply to people using the dashboard. SDKs, the log agent and cron check-ins authenticate with the project's keys — see Server Secret & Server Routes.

Free Allowance and Wallet#

Abrova Trace counts error events per month for your organisation: every error it receives, repeats of a known issue included. On screen, the events of one cause are grouped into one issue, so the list stays readable.

Every month 50,000 error events are free. Above that, each started 1,000 events costs 3,000 Toman, deducted once a day from your organisation's prepaid wallet — see Pricing. There is no subscription. On the free plan, up to 1,000 new issues a month are also stored.

When the free amount is used up and the wallet has no balance (pay as you go stays on for 3 more days after the balance reaches zero):

• New events are not stored until the free amount resets at the start of the next month, or until you top up the wallet.
• Nothing already stored is deleted.
• Your apps are never disturbed. The API still answers success (200), with a body that says the event was not stored, so no SDK retries, queues or logs an error:

{
  "status": "dropped",
  "code": "plan_limit_reached",
  "metric": "error_events_monthly",
  "limit": 50000,
  "used": 50000,
  "resets_at": "2026-11-01T00:00:00.000Z"
}

(limit and used are example values; they show your organisation's free amount and use this month.)

Performance monitoring (spans and Web Vitals) is part of pay as you go and does not count as error events.

Search & Filtering#

• Text Search — Search across error messages, platform, and environment
• Combined Filters — Combine status, frequency, time range, platform, environment, release and text search
• Pagination — Navigate through large error lists efficiently

Best Practices#