DASHBOARDS
- Known question
- Known query
- Repeated view
PRODUCTION EVIDENCE
See the evidence. Understand how it connects.
Explore metrics, logs, traces and production changes in shared context. AutoObserve connects telemetry across services, dependencies and changes so you can move from changed behaviour to relevant evidence without rebuilding the investigation.
THE EVIDENCE LAYER
Telemetry is evidence—not the conclusion.
Each evidence class describes a different part of production behaviour. AutoObserve preserves those distinctions while connecting them through shared production context.
Production
Changed behaviour
Metric
Error rate ↑
Log
Timeout pattern
Trace
Failed request
Event · Deploy
Correlated evidence
METRIC
Measured behaviour
LOG
Recorded event or context
TRACE
Request execution
EVENT
Production change or state transition
TOPOLOGY
Runtime relationship
INCIDENT
Operational situation
EVIDENCE
Something relevant to an investigation
Observability provides the evidence. AutoObserve builds operational understanding from it.
Changed behaviour fans out into evidence classes—then reconnects.
UNIFIED EXPLORATION
Change the signal—not the investigation context.
Service, environment, and time window survive every transition between metrics, logs, traces, events and topology.
- checkout-api
- production
- 14:25 → 14:35
- checkout-degradation
Historical
Understand how production behaviour is changing.
Same service · same environment · same window
checkout-api
p95 request latency
+184% from baseline
- Baseline
- 241 ms
- Observed
- 684 ms
- Peak
- 812 ms
- Change
- v2.14.7
Related
- 3 log samples
- 312 failed spans
- 1 production change
LOGS evidence
TRACES evidence
EVENTS evidence
DASHBOARDS & EXPLORATION
Monitor known questions. Explore when production surprises you.
EXPLORATION
- Unexpected behaviour
- Follow evidence
- Change evidence type
- Investigate
CORRELATION
Connect the evidence around production behaviour.
Metrics, logs and traces establish credibility. Correlation establishes differentiation—with explainable relationship reasons, not opaque scores.
Incident
Checkout degradation
Metric
+184%
Log
Pattern
Trace
Failed spans
Related change · v2.14.7
Topology · Checkout → Payment path
Investigation
CORRELATION EXPLORER
Explore related evidence in one production window.
OPEN STANDARDS
Built around OpenTelemetry—not proprietary instrumentation.
Instrument once. Keep control of your telemetry.
OPEN TELEMETRY
Instrument once. Send via your Collector.
OpenTelemetry delivers production signals. AutoObserve transforms them into correlated evidence — identity, quality and connect paths are on the OpenTelemetry page.
TELEMETRY ACCESS
AutoObserve
Multi-DSL
- Prometheus
- Loki
- Tempo
Explore and investigate production evidence across existing telemetry systems without forcing every team into one proprietary query model.
FROM EVIDENCE TO UNDERSTANDING
Observability provides the evidence. AutoObserve builds operational understanding from it.
Evidence → Diagnosis → Decision → Response → Verification
- Evidence
- Correlation
- Topology context
- Investigation
- Hypotheses
- Incident decision
- Response
- Verification
AIDDE
Turn production evidence into incident candidates.
INVESTIGATION
Turn correlated evidence into supported explanations.
TOPOLOGY
Understand evidence in runtime dependency context.
Autonomous response is a closing step on this page—not the centrepiece.
TRUST
Never hide the evidence behind the conclusion.
Inspectable
Open the telemetry and query behind every evidence item.
Source-aware
Know where evidence came from.
Time-aware
Preserve the exact production window.
Uncertainty-aware
Surface missing or partial telemetry.
TELEMETRY COVERAGE
TRACE COVERAGE
64%
PARTIALPARTIAL — payment-service
Payment-path evidence incomplete. Investigation confidence may be reduced.
Window: 14:31 → 14:33