Skip to content
BENIBIX Learn

Logging

Infrastructure📈 Monitoring & ObservabilityTelemetry Signals

Also known as Log, Logs, Log File, Application Log, Structured Logging

Writing down what a program does, one timed line per event.

Think of it like

It is like a ship's diary. Each line says what happened and when.

Example

A payment fails for one buyer. Jack searches the logs for the order number and finds the line saying the card was refused.

Why it matters

When something breaks, the log is often the only record of what took place.

Definition

Logging is writing down events, one line at a time, as a program runs. Each line, called a log entry, has a time, a level and a message. It might say a user logged in, or a payment failed. The lines go to a file or to a tool that gathers logs from many servers. Logs are the place to look for the details of one event.

Example code

json
{"time": "2026-11-16T09:14:02Z", "level": "error", "msg": "payment failed", "order": 4182}
One structured log line. Each part has a name, so a tool can search by order or level.
Logs are the left panel. They tell the story of one event in words.

Common mistake

Writing passwords or card numbers into logs. Many people can read logs, and they are kept for a long time.

Key takeaways

  1. 1
    Time on every line. So events can be put in order.
  2. 2
    Structured. Named fields are easy to search.
  3. 3
    Gathered in one place. Logs from all servers, searched together.

Compare