Skip to content
Observability diagram with an OpenTelemetry collector, log, metric and trace stores, alert rules and on-call paging on a card over a photo.

Observability Architecture

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
5
Difficulty
Intermediate
Updated
November 8, 2026

Every slide (5)

Overview

Each service sends logs, metrics and traces through the OpenTelemetry SDK to a collector, without waiting for a reply. The collector batches the signals, drops sensitive fields and sends each type to its own store. Alert rules run threshold queries against the metrics database every minute. A breached critical rule sends a page to the paging service, which notifies the on-call engineer and escalates if the alert is not acknowledged in time. The engineer then opens the dashboards and traces to find the cause.

The design point is to alert on symptoms users feel, such as error rate and latency, and to use logs and traces to explain the cause. Sampling keeps every error and favours slow requests, which keeps trace storage affordable. The collector is the only component that holds exporter credentials and the one place to redact personal data. To adapt it, swap in your own vendor or open-source tools and keep the collector and the three stores.

Useful for

  • Setting alerts on error rate and latency for a customer-facing API
  • Choosing retention periods for logs, metrics and traces
  • Stopping personal data reaching logs with a collector redaction step

What's included

  • A designed cover slide
  • The diagram: 11 components and 11 connections as editable shapes
  • A components table and the 7-step data flow
  • A legend with notes
  • The same diagram as a draw.io (diagrams.net) file

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Rename API service, Worker service, Telemetry collector and the other boxes inside Production workloads to your own components, and delete the ones your system does not have.

  3. 3

    Rewrite the 7-step data flow and the 6-row components table so they match the arrows you keep.

  4. 4

    For the draw.io version, download observability-architecture-diagram.drawio and open it at app.diagrams.net.

What you need

Requirements

  • A Google account for Google Slides, or the free draw.io (diagrams.net) editor

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)
  • draw.io / diagrams.net (.drawio file)

Questions

What is the OpenTelemetry collector for?

The collector receives logs, metrics and traces from services, processes them and exports them to one or more back ends. Here it batches, samples and redacts before routing each signal to its own store.

Why alert on symptoms rather than on every resource metric?

Users feel errors and slow responses, not high CPU on its own. Alerts on symptoms such as SLO burn rate page the team when customers are affected, which cuts noise from harmless spikes.

What is a trace id and why put it in logs?

A trace id is an identifier carried by every span of one request as it crosses services. Writing it into each log line lets an engineer jump from a log entry to the full request trace.

  • #infrastructure-diagram
  • #architecture-diagram
  • #google-slides
  • #drawio
  • #diagram-template
  • #free-template

More infrastructure diagram templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…