Stratum guide
View observed topology from Prometheus
Turn OpenTelemetry service-graph metrics into a read-only current-state view and fork useful snapshots into designs.
The telemetry view helps teams compare architecture ideas with observed service relationships without making Stratum a trace explorer or monitoring replacement.
What Stratum reads
The Prometheus connector queries pre-aggregated OpenTelemetry service-graph metrics. A layered pipeline fetches metrics, parses labels, normalizes services and dependencies, and converts the topology into Stratum node and edge objects.
Configure the integration
- Open Admin console → Integrations.
- Enable Prometheus and provide its approved endpoint and authentication settings.
- Configure namespaces, component filters, excluded health endpoints, and data-client visibility.
- Test the connection before making the view available.
Inspect and fork
The generated topology is read-only and can refresh as telemetry changes. Filter noisy services, inspect inferred dependencies, then choose Create design from current state to copy one snapshot into a normal editable design. Telemetry history is not copied.
Know the boundary
- No individual trace exploration.
- No claim that absence of telemetry proves absence of a dependency.
- Sampling, missing instrumentation, label quality, and background traffic can affect the model.
- Once forked, users can clean up naming, boundaries, and missing architecture context.