The issue-first loop.
Capture structured events, fingerprint them into issues, and inspect SDK-native performance — transactions, RED, DB/HTTP spans, Web Vitals, and release health — in a focused dashboard.
From noise to a shortlist
Apps send events with a project API key. Talaria groups them. Your team decides what to fix next — not which duplicate to scroll past.
01
Event
One captured occurrence — an exception or structured log from your app.
02
Fingerprint
Server-side identity for deduplication. Clients never compute it.
03
Issue
A grouped problem with counts, status, severity, and first/last seen.
04
Alert
Rules and notifications so the right people know when issues need attention.
Organizations & projects
Run multiple apps under one workspace — ideal for product teams and agencies. Invite teammates as admin, member, or viewer without ever sharing API keys.
Ingest & API keys
Every project gets a scoped key shown once at creation (tal_live_…). Use an SDK or raw HTTPS ingest — never embed keys in public frontends.
Project settings
storefront
API key
tal_live_••••••••••••3f9a
Shown once at creation. Project-scoped ingest credential.
Role
Admin
Members
4 invited
Issues
storefront
- 1,284erroropen
TypeError: Cannot read properties of undefined
production
- 412fatalopen
TimeoutError: upstream request timed out
production
- 56warningresolved
Unhandled rejection in payment webhook
staging
Issues & events
Open, resolved, ignored. Filter by severity, environment, and release. Drill into individual events when you need the stack — then mark the issue done and move on.
SDK-native performance
Official SDKs capture transactions and child spans — DB queries, outbound HTTP, Web Vitals — so you can inspect waterfalls, RED metrics, and release health next to the issues they belong to. No host agent. Not host/k8s metrics, continuous profiling, or a log platform. Read the SDK-native APM guide or the full Learn series.
Alerts
Create alert rules for new or reopened issues and metric thresholds. Notify your team by email — and by webhook or Slack on paid plans — so triage stays ahead of the noise.
Session replays, metered clearly
Retained session replays are a second billable meter — counted by finished replay, not minutes or gigabytes. Event and replay budgets stay separate, so a replay spike cannot burn your event quota.
Architecture
Client or SDK → API (api.newtalaria.com) → fingerprint and traces → dashboard (one.newtalaria.com). One clear path from capture to triage and performance.
See the product for yourself
Start free on Developer, or dig into docs first — either way, you can triage real issues in minutes.