SpecsModelExploreRequirements
SpecsModelExploreRequirements
Observability
Overview
Guide
Twin streams
IDproduct.platform.observability
DescriptionMetrics, logs and traces for the platform.
Keyobservability
Typemicroservice:service
Statusactive
TeamPlatform Engineering
Owner
platform@iotgateway.example
TechnologiesOpenTelemetry Collector, Prometheus, Grafana Loki, Grafana Tempo
Tags
Table of contents
Guide
Observability
Internal structure
How signals flow
Pipelines
Retention at a glance
Requirements

Attributes

retention15d
slo99.5%

Guide

Observability

Observability collects the three signal types — metrics, logs and traces — from every service and makes them queryable. It is how on-call engineers answer “is the fleet healthy?” and “why did this request fail?” without SSH-ing into a box.

Three pipelines, one collector edge

Every service ships signals to a local OpenTelemetry Collector, which fans them out to the right backend. Splitting metrics, logs and traces keeps each storage tier tuned to its very different access pattern.

Internal structure

Could not build diagram for model "example-iot".

How signals flow

Pipelines

Metrics Pipeline

Prometheus scraping and remote write for time-series metrics.

Log Pipeline

Loki + Vector aggregation for structured logs.

Trace Pipeline

Tempo + OTel collectors for distributed traces.

Retention at a glance

High-resolution series kept 15d; downsampled rollups longer for capacity planning.

Requirements