ERR-CAPComing
Exception capture with context
Unhandled exceptions from your apps land in SolidOps with their full stack trace, the runtime context, and enough metadata to reproduce the failure. Nothing is quietly swallowed.
Coming · Error collection
Errors, grouped and wired in.
Sentry-style exception capture with stack traces, fingerprint grouping, and a direct path into your incidents and alerts. This one is on the roadmap, not shipped. Here is the plan.
Buying the lifetime plan now reserves your base ingest allowance, so error collection is included at that base the day it ships. The metered charge only ever applies to ingest volume past the base, and only once the feature is live.
Error stream · concept
not built yetEXCEPTTypeError: Cannot read properties of undefined147×first 2d ago
EXCEPTReferenceError: fetch is not defined23×first 6h ago
EXCEPTUnhandledPromiseRejection: Network request failed9×first 41m ago
Illustrative · how a grouped issue list might readComing
The plan · 4 pieces
What error collection will do.
These are the pieces we intend to ship. Documented so the direction is clear, not so it reads as finished. Each one is planned; none of it runs today.
ERR-GRPComing
Grouping by fingerprint
Similar exceptions fold into one issue with a count and a first-seen and last-seen timestamp, so the same crash thrown a thousand times appears once, not as a flood of duplicate noise.
ERR-INCComing
Wired into incidents and alerts
A spike in a grouped error can open an incident and fire an alert through the same channels already configured for uptime. One place to see the whole state of your stack, not two separate dashboards.
ERR-SDKComing
SDK delivery
A small SDK to drop into your app, or a lightweight agent for server-side exception capture. Outbound-only. No inbound surface to open up on the host.
How the ingest stays honest
A base allowance is included.
You only pay for volume past it.
Ingest events are the real cost in error tracking. Here is exactly how the charge will work, written down before the feature ships, so there is no surprise on the bill later.
- Base allowanceIncluded
A base monthly ingest-event allowance comes with the lifetime plan at no extra cost. Buy now and that allowance is reserved for you the day error collection ships.
- Above the baseMetered monthly
Only ingest volume beyond the base allowance is billed, and only by how much you actually send. No tier to guess at up front, no waste on capacity you never use.
- Metered cost today$0 for everyone
Error collection does not exist yet, so nothing is metered yet. The per-event charge starts the day this feature ships, never before that.
Ingest · concept
not billed yetHow a monthly bill would readillustrative
Base · includedOver base · the only billed slice
Your charge today$0.00
illustrative meter · figures are a concept, not a bill
Platform fit · planned
One surface for all your signals.
The goal is to wire errors into the same incident and alert system that already handles uptime. A spike in exceptions opens one incident, not a separate Sentry notification alongside a separate uptime alert.
What ships todayLive
Monitoring, incidents, and alerts are live. If an uptime check fails, an incident opens and an alert fires. That surface is already running.
What errors will addComing
When error collection lands, an exception spike becomes another signal that can trigger the same incident and alert paths. Your uptime numbers and your error counts will sit side by side, not in two separate tools.
The alternative this replaces
Today you probably run Sentry for errors and something else for uptime. When both fire at once you get two separate alerts for what is usually the same outage. The plan is to collapse that into one incident with both signals attached.
Signal flow · concept
not built yetMONUptime check failsLive
ERRError spike detectedComing
ALRAlert fired to your channelLive
INCOne incident openedLive
Illustrative · the planned signal path
Status · roadmap
Error collection is not built yet.
This page is here so you know where SolidOps is headed, not so it looks finished. No exceptions are being captured today, no grouping runs, and no incidents are opened by error signals. When error collection ships, this becomes a real feature page and the metered ingest charge begins for volume past the base allowance. Until then, the honest answer is that the work is ahead of us.
Coming · on the roadmap
Lock in the lifetime plan now. Get error collection at the base when it lands.
Monitoring, incidents, and alerts are live today, and the lifetime plan includes the base error ingest allowance the moment error collection ships. Buy once, and grow into the platform as each piece comes online.