Catalog categoryOpen record · no account required
Observability and telemetry
Monitoring, logging, tracing and alerting platforms. The tools engineering teams rely on to see failure, which makes their own reliability harder to notice from the inside.
- Dependencies under observation
- 4
- Taxonomy position
- observability
- Category scope
- Public catalog records grouped by what they are
Records in this category
Observed state is each dependency's own verdict from the most recent observation of its primary listed endpoint. There is deliberately no category roll-up: unlike endpoints do not share a meaningful average.
Revalidated every 60 seconds
DependencyObserved stateLast observation
Datadog
Responding
- Last observation
- 28m ago
Grafana Cloud
Responding
- Last observation
- 28m ago
PagerDuty
Responding
- Last observation
- 28m ago
Sentry
Responding
- Last observation
- 28m ago
4 dependency records in this category. Times are relative to the most recent completed observation; open a record for exact UTC timestamps.
How to read this page
What this grouping does and does not claim.
- Grouping only
- A category is a directory position, not a measurement. It groups dependency records so engineers can find the class of infrastructure a service belongs to; it does not merge their data into one figure.
- Observed state
- From the most recent observation of each dependency's primary listed endpoint, exactly the definition used on the observatory index. Open a record for the finer verdict, the full telemetry and the incident history.
- Independence
- Every figure on the records under this category originates from a RELIASTRA probe. A vendor's own status text is never read or mirrored.
Full catalog: observatory index.