Skip to content
BENIBIX Learn

Instrumentation

Infrastructure📈 Monitoring & ObservabilityTelemetry Signals

Also known as Code Instrumentation, Auto-Instrumentation, Zero-Code Instrumentation

Adding code to a program so it tells you what it is doing.

Think of it like

Think of it like fitting sensors to a machine. Then the machine can tell you how it is doing.

Example

Lucy adds one library to her web app. With no other changes, every request now makes a trace that shows the database calls inside it.

Why it matters

A program can only be watched if it reports. What you add now decides what you see when it breaks.

Definition

Instrumentation is adding the code that makes a program send out telemetry. Without it, a program does its job but says nothing about how it went. It can be written by hand, with a few lines that start a timer or count an event. It can also be added with no code changes, by a library or an agent. Most teams start with the automatic kind and add their own where they need more detail.
The instrumentation is the code inside the app box. Without it, nothing flows out to the right.

Common mistake

Adding it only after an outage. By then, the data from the outage is already gone.

Key takeaways

  1. 1
    Makes it talk. The program reports what it does.
  2. 2
    By hand or automatic. Code you write, or a library.
  3. 3
    Decides what you see. Missing data cannot be added later.