Centralized logging system
A centralized logging system collects and manages logs from multiple applications or services in a shared location for storage, search, correlation, and analysis.
Kafka for Architects
A centralized logging system collects log records from multiple applications or services into a common system for storage, search, and analysis.
- How it is used
- Centralizes logs from distributed applications to support real-time oversight, failure investigation, search, and analysis.
- How deep it goes
- Explains the end-to-end data flow and architectural rationale but stops short of implementation details.
- Examples
- Uses a Customer 360 ODS with heterogeneous services and an application-to-Kafka-to-Elasticsearch-to-Kibana flow.
- What you can do after
- Operate unified log oversight and investigate events through indexed search and visual interfaces.
Read how Kafka for Architects explains centralized logging system →
Learn Docker in a Month of Lunches, Second Edition
Centralized logging is a logging architecture in which logs from multiple applications or containers are collected and managed in a shared system.
- How it is used
- Collects container logs in one searchable system for operational visibility across applications.
- How deep it goes
- Explains the collection pipeline, Compose deployment, driver configuration, Kibana indexing, and structured search.
- Examples
- Uses timecheck and image-gallery containers, Fluentd commands, Compose files, Kibana data views, and searchable Elasticsearch indexes.
- What you can do after
- Operate and configure a Docker logging stack that forwards container output to Elasticsearch for Kibana-based searching.
Read how Learn Docker in a Month of Lunches, Second Edition explains centralized logging system →
ASP.NET Core in Action, 3e
Centralized logging is a logging arrangement in which application instances send their logs to a shared location separate from the applications.
- How it is used
- Supports production troubleshooting across multiple application instances without manually retrieving separate server log files.
- How deep it goes
- Explains the arrangement, operational rationale, and provider choices, but defers controlling the volume of production messages.
- Examples
- Uses Azure App Service, elmah.io, Seq, and an ASP.NET Core WebApplicationBuilder provider configuration.
- What you can do after
- Operate/configure ASP.NET Core logging providers that send messages to a shared external destination.
Read how ASP.NET Core in Action, 3e explains centralized logging system →
Related concepts
- fluentduses · Fluentd is an open-source data collector that gathers, processes, transforms, and routes logs and other machine-generated event data through pluggable integrations.
- monitoringaddresses · Monitoring is the ongoing observation and measurement of a system’s behavior, state, or operational signals to assess its condition and detect changes or problems.
- log aggregationuses · Log aggregation is the collection and consolidation of log records from multiple sources into a common destination for storage, search, or analysis.
- security information and event managementimplemented by · Security information and event management is a class of security systems that centrally collects, correlates, and analyzes security events and log data to support monitoring and response.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.