SpecsModelExploreRequirements
SpecsModelExploreRequirements
Log Pipeline
Overview
Guide
Twin streams
Links and Communications
IDproduct.platform.observability.log_pipeline
DescriptionLoki + Vector log aggregation.
Keylog_pipeline
Typecomponent
Statusactive
TeamPlatform Engineering
Owner
platform@iotgateway.example
TechnologiesGrafana Loki, OpenTelemetry Collector
Tags
Table of contents
Guide
Log Pipeline
Flow
What gets logged
Links and Communications
Requirements

Attributes

ingest_rate200k lines/s
retention30d

Guide

Log Pipeline

The Log Pipeline collects structured logs from every service, ships them through Vector for parsing and enrichment, and stores them in Grafana Loki for fast, label-indexed search.

Index labels, not lines

Loki indexes only a small set of labels (service, level, region) and stores the log body compressed. That keeps ingest cheap at 200k lines/s while still letting you grep within a label stream.

Flow

What gets logged

  • Request and error logs with a trace_id for correlation.
  • Audit events from the Secrets Manager.
  • Lifecycle events (deploys, config changes).

Every log line carries the trace_id so a noisy error can jump straight into the Trace Pipeline for the full request story. Hot logs are retained 30d.

Links and Communications

1 incoming link

Incoming Links(1)

Source objectLabelLink typeRelationRaw idRequiredDescription
Trace Pipeline

example-iot.product.platform.observability.trace_pipeline

component
correlates with—linksproduct.platform.observability.log_pipeline——

Requirements