Skip to content

Log Aggregation

In one line

Log aggregation centralizes logs from all services into one searchable store — for debugging, analysis, and alerting.

In simple words

Log aggregation collects logs from all servers and services into a single central store, where you can search, filter, and analyze them. Instead of SSH-ing into individual servers, you query one central system.

Features: collection, indexed storage, search, visualization, alerting. Popular: ELK (Elasticsearch, Logstash, Kibana), Loki + Grafana, Datadog.

Example

bash
# Fluentd ships logs to Elasticsearch
# Search in Kibana:
# service:api AND level:error AND @timestamp:[now-1h TO now]
# Find all API errors in the last hour across all servers

Fluentd tails log files on each server and ships to Elasticsearch. Kibana lets you search all logs from one place — no SSH needed.

Common confusions

  • Confused with: Monitoring

    The difference: Log aggregation collects and searches text logs. Monitoring collects numeric metrics and triggers alerts. Logs are for debugging why; metrics are for detecting when.

Related terms

Related Resources

Related Lessons

Decode error messages

Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.

View errors

← Back to glossary