Selecting an error tracking and reporting service is not always easy. There are three main criteria for good error-tracking software:
- ability to group similar stack traces into one entity
- support for source maps (because your stack traces will likely be minified)
- ability to export stack traces
Let's take one popular example of such systems, Sentry.io, and a couple of corporate-level ones: AWS CloudWatch RUM and Splunk RUM.
Sentry.io:
| Error grouping | Source maps | Notifications | Self-Hosted | Export |
|---|---|---|---|---|
| ✅ | ✅ | ✅ | ✅ | ❌ |
AWS CloudWatch RUM:
| Error grouping | Source maps | Notifications | Self-Hosted | Export |
|---|---|---|---|---|
| ✅ | ❌ | ❌ | ❌ | ✅ |
Error grouping:
No source maps:
Splunk RUM:
| Error grouping | Source maps | Notifications | Self-Hosted | Export |
|---|---|---|---|---|
| ❌ | ❌ | ❌ | ❌ | ✅ |
No error grouping:
No source maps:
But Splunk RUM has strong features for tracking user actions step-by-step:
CloudWatch RUM and Spunk RUM are not focused on error tracking only, and they don't have notifications about errors. You need some extra time and skill to configure them (this might not be possible).
Top comments (0)