liveBook · Manning

Log aggregation

As explained in Secure APIs

A log aggregator is a system that receives log records from multiple sources for centralized storage, search, and analysis.

Log aggregation collects log records from application and infrastructure sources, then routes them to centralized storage for searching and security analysis. section 11.5

A practical pipeline writes logs to stdout, treats them as streams, and uses a router such as Logplex or Fluentd to deliver them to an aggregator. Container deployments can run the collector beside the application as a sidecar. section 11.5

Use the collected records to:

  • Investigate requests associated with malicious injection attempts, optionally annotating records to identify the attack. section 11.5
  • Remember that logs alone may miss attacks spread across many requests. section 11.5

How Secure APIs covers it

How deep it goes
Explains the stdout-to-router-to-aggregator pipeline and sidecar deployment, but stops short of multi-request attack detection.
Examples
Uses stdout streams, Fluentd or Logplex, a sidecar collector, and an order endpoint that excludes credit-card data.
What you can do after
Operate/configure a collection pipeline and reduce sensitive-data exposure in request logs.
How it connects
Links request logging with malicious injection detection, log routing, sidecar containers, and API security.

Also explained in

Compare how 3 books explain log aggregation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.