Application Errors

Catch every error before your users do

Real-time error tracking software for modern applications. Capture every exception with full stack traces, source map support, and contextual breadcrumbs. Smart grouping cuts through noise so your team fixes what matters — not what duplicates.

platform.mihari.io/errors
Unresolved (23)
Resolved
Ignored
Search errors...
Last 24h
TypeError: Cannot read property 'id' of undefined
342x
checkout.ts:1422 min ago
frontend
89 users
RangeError: Maximum call stack size exceeded
128x
tree-utils.ts:6715 min ago
frontend
34 users
NetworkError: Failed to fetch /api/v2/billing
87x
api-client.ts:231 hr ago
frontend
12 users
SyntaxError: Unexpected token in JSON at position 0
23x
parser.ts:4453 hr ago
api
8 users
Stack TraceTypeError
at processPayment (checkout.ts:142)
at handleSubmit (form.ts:87)
at onClick (button.tsx:23)
at dispatchEvent (react-dom.js:4182)
Breadcrumbs
14:21:02Page load /checkout
14:21:08Click: "Add to cart"
14:21:12XHR POST /api/cart
14:21:15TypeError thrown
Real-Time Error Capture

Full context for every exception

When an error occurs, context is everything. Mihari's crash reporting automatically captures the complete stack trace, browser and OS information, user session data, and a timeline of breadcrumbs leading up to the exception. Your team sees exactly what happened, in what order, and for which user — without reproducing the bug manually.

  • Full stack traces with original source code via source map support
  • User session replay with breadcrumbs timeline leading to the error
  • Browser, OS, device, and network metadata captured automatically
  • Custom context tags for environment, feature flags, and A/B tests
  • Lightweight SDK (<10KB gzipped) with zero impact on page performance
Error Detail
Assign
Resolve

TypeError: Cannot read property 'id' of undefined

First seen 3h ago
342 occurrences
89 users affected
Stack Trace
Breadcrumbs
User Context
Tags
processPaymentcheckout.ts:142:18
140 |  const charge = await stripe.charges.create({
141 |   amount: cart.total,
142 |   customer: user.subscription.id,
143 |   currency: 'usd',
144 |  });
handleSubmit — form.ts:87:5
onClick — button.tsx:23:12
JC
jane@acme.com
Chrome 122 / macOSIP: 203.0.113.x
Grouped Issues
3,847 events grouped into 12 issues
TypeError: Cannot read property 'id' of undefined
+180%
342
checkout.ts:142
89 users
2 min ago
RangeError: Maximum call stack size exceeded
+45%
128
tree-utils.ts:67
34 users
15 min ago
NetworkError: Failed to fetch
87
api-client.ts:23
12 users
1 hr ago
Smart Error Grouping

Noise down, signal up

A single bug can generate thousands of identical error events. Mihari's application monitoring uses fingerprinting algorithms to intelligently group duplicate exceptions into unique issues. See occurrence counts, trend indicators, and affected user counts at a glance. Prioritize by impact, not by volume — and assign issues to the right team member directly from the dashboard.

  • Fingerprint-based grouping that merges duplicate errors into unique issues
  • Trend indicators showing errors that are growing, stable, or declining
  • Affected user count and impact score for data-driven prioritization
  • Custom grouping rules for fine-tuned control over issue classification
  • Merge and split issue groups manually when automatic grouping needs adjustment
Source Maps & Context

Debug with original source code

Minified stack traces are useless. Upload your source maps to Mihari and see the exact original line of code that caused each error. View local variable values, function arguments, and surrounding code context. Source map support works with JavaScript, TypeScript, and any language that compiles to JS. Your source maps are encrypted at rest and never exposed publicly.

  • Upload source maps via CLI, API, or as part of your CI/CD pipeline
  • View original TypeScript, JSX, or compiled code with error line highlighted
  • Local variable inspection showing values at the exact frame of failure
  • Source maps encrypted at rest and never publicly accessible
  • Support for JavaScript, TypeScript, and any compile-to-JS language
src/services/checkout.ts
Line 142
138
async function processPayment(cart, user) {
139
  try {
140
    const charge = await stripe.charges.create({
141
      amount: cart.total,
142
      customer: user.subscription.id,
143
      currency: 'usd',
144
    });
145
    return charge;
Local Variables at Line 142
cart={ total: 4999, items: 3 }
user={ id: 847, subscription: undefined }
Release Tracking

Know which deploy broke things

Tag errors by release version and see exactly when regressions were introduced. Mihari overlays deploy markers on your error rate timeline so you can instantly correlate spikes with specific releases. Track error budgets per release, identify the commit that caused a regression, and decide whether to roll back — all from one view.

  • Deploy markers overlaid on error rate timelines for instant correlation
  • Per-release error budgets and regression detection with auto-alerts
  • Commit-level resolution linking errors to the exact code change
  • Automated rollback recommendations when error rates spike post-deploy
Error Rate — Last 7 Days
12080400
MonTueWedThuFriSatSun
v2.14.0Wed 10:32 AM+340% errors
v2.14.1Thu 2:15 PM (hotfix)-92% errors
Integrations
GitHubConnected
Configure
Auto-create issues from errors. Link commits to error resolutions. Track suspect commits.
SlackConnected
Configure
Real-time error notifications in your team channels. Resolve and assign errors from Slack.
JiraConnected
Configure
Create Jira tickets from error groups. Sync status between Mihari and your project board.
PagerDutyNot connected
Connect
Integrations

Works where your team works

Errors are only useful if the right people see them. Mihari integrates with your existing development workflow — GitHub for automatic issue creation and suspect commit detection, Slack for real-time notifications, Jira for ticket management, and PagerDuty for critical alert escalation. Resolve errors without leaving the tools you already use.

  • GitHub: Auto-create issues, link commits, detect suspect changes
  • Slack: Real-time notifications, in-channel resolution and assignment
  • Jira: Two-way sync between error groups and project tickets
  • PagerDuty and Opsgenie: Escalate critical errors to on-call engineers
  • Webhooks: Send error events to any custom endpoint or internal tool

Performance monitoring, built in

Errors don't happen in isolation. Mihari tracks transaction performance alongside exceptions so you can see whether an error is causing slowdowns — or whether a slow endpoint is triggering timeouts and cascading failures. Monitor Apdex scores, throughput, and response times without deploying a separate APM tool.

Transaction Tracing

Trace every HTTP request through your application. See database queries, external API calls, and cache hits.

Apdex Scoring

Industry-standard user satisfaction scores. Set custom thresholds per endpoint and alert on degradation.

N+1 Detection

Automatically detect N+1 query patterns and slow database queries. Get suggestions for optimization.

Stop flying blind in production

Every undetected error costs you users and revenue. Start catching exceptions, tracing root causes, and resolving issues before your customers notice. Free tier available.