How Maersk is Navigating the Seas of Observability with the LGTM Stack
summary
Maersk consolidates logs, metrics, traces and RUM into a central Maersk Observability Platform (MOP) built on the LGTM Stack plus Grafana Faro, running on Azure AKS; ingestion enforces labels via a write proxy that drops invalid data, queries are blocked if they would read >200GB, and two custom components (Guard and Wizard) handle write- and read-side validation. Platform splits services into separate clusters to raise uptime toward 99.5% availability, adds a Flutter mobile SDK with offline batching, sees ~460% mobile growth, and contributes fixes back to open source.
AI-written summary · about
chapters (7)
- 0:00Introductions
- 3:00About Maersk
- 5:00Problem statement and challenges
- 6:35Maersk observability platform overview
- 8:12Platform capabilities: Ingestion, Query, RUM
- 23:10Reliability
- 26:20What's next?
related talks
17mImplementing Open-source Observability within Maersk
28mMonitoring Stack was yesterday – Observability Platform at scale!
33mBeyond Monitoring: The Rise of Observability Platform
56mFull-stack observability and application monitoring with
01h 00mObservability made painless: Go, Otel & LGTM stack
34mThe Grafana Stack: Building a Highly Available, Scalable Observability Platform
13mArchitecting an open observability stack
31mCharting New Frontiers: The Evolution of Observability in Cloud Environments