CompCode Academy

Lesson 3 of 4 · Free to read

Session guide

Session guide — Observability Foundations: LGTM + LocalStack Order Pipeline

Visual companion to the Lesson. Use in study groups or when you want the diagram first.

Watch

Course video

Open on YouTube
How Prometheus Monitoring works — Prometheus scrape, TSDB, and alert architecture used in MNCs.

Course video

Open on YouTube
OpenTelemetry Deep Dive (Big Tent) — Standards, tracing, and why OTel is the 2026 vendor-neutral data plane.

Flow

60-second summary

At 3am an order API returns 202 but nothing lands in S3. Fixed dashboards say “CPU fine.” Observability means you can ask a new question — which hop broke? — without shipping code.

MNC 2026: MNCs run vendor-neutral OTLP into Grafana LGTM (Loki, Grafana, Tempo, Mimir) plus Prometheus scrape and Pyroscope profiles. LocalStack lets you rehearse SNS→SQS→S3 without a cloud bill.

Chunks

  • Questions first, then instrumentation: Name user-facing SLIs, list incident questions, then derive the minimum telemetry. “Collect everything” burns budget and signal-to-noise.
  • Four signals, four jobs: Metrics: is it broken / how bad. Traces: where. Logs: why. Profiles: which code. Correlate by trace_id in Grafana.
  • Cardinality is a cost decision: Never put unbounded IDs (order_id, user_id) on metric labels — put them on span attributes or log fields.
  • One lab bench for every later phase: Build day01-style compose once. Every later phase extends this tree.

Session guide — Observability Foundations: LGTM + LocalStack Order Pipeline.

New free lessons and course updates. Unsubscribe from any email.