Observability Observability™
Who watches the watchers? We do. Then we watch that.
Observability Observability™ wraps every monitoring tool you own in another layer of monitoring, then monitors that layer, until the dashboards have dashboards and every alert has a parent.
What it does
Recursive instrumentation
Each level of monitoring emits metrics about the level below and receives alerts from the level above. Depth is configurable; the default is "yes."
Alert lineage
Every page shows the full ancestry of the alert, back to the original alert, which was about alerting.
Self-paging
The platform pages the on-call engineer when it detects that it has not paged anyone in a while.
How it works
- STEP 01
Wrap
Connect any monitoring tool. Observability Observability™ observes it.
- STEP 02
Recurse
A new layer is added on a schedule, or whenever a dashboard is opened.
- STEP 03
Escalate
Alerts flow upward until they reach the CIO or the top of the recursion, whichever is quieter.
Key metrics
- layers
- ∞
- root cause (alerting)
- 1
- a.m. median page time
- 3:00
- MTTR coverage (the time is covered, not reduced)
- 100%
Compliance and sovereignty
Every layer is logged in CryoLake™. Logs of the logging are retained one level longer than the logs.
Pricing
| Pricing | Observability Observability |
|---|---|
| Not included | |
| Starter | Not included |
| Growth | up to seven layers |
| Enterprise Plus | unbounded, plus a layer that monitors the invoice |
Customer story
"We finally know why we were paged. We were paged because we were paged."
FAQ
Does this replace our existing monitoring?
It respects your existing monitoring by monitoring it.
How many layers do we need?
One more than you have.
What is the root cause of most alerts?
Alerting.
Can it reduce noise?
It can categorize noise, which is the first step toward a dashboard about noise.
Start with one module or all nine. The invoice is the same shape.
Build your slopRelated modules
ThroughputIQ™
Caffeine throughput intelligencePredictive insight into your organization's caffeine throughput, correlated against revenue, morale, and parking. Correlation is not causation, but it is a dashboard.
Explore ThroughputIQ →LayerCake™
Full-stack reference architectureBase (infrastructure), filling (microservices), icing (middleware). Served in slices, scaled horizontally, never explained to the board.
Explore LayerCake →Resurface™
Data resurfacingSmooths your data lake between reporting periods. Nobody knows what it actually does, but the lake looks incredible afterwards and the auditors stop asking.
Explore Resurface →