How deeply does ASP.NET Core in Action, 3e cover centralized logging system?

Explains the arrangement, operational rationale, and provider choices, but defers controlling the volume of production messages.

Centralized logging system

As explained in 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.

A centralized logging system sends logs from every application instance to one shared location outside the applications. This avoids collecting files manually from multiple production servers and reduces dependence on remote access, disk space, and file permissions. section 26.3

The destination can be a cloud provider or a third-party log aggregator. Each application instance uses a logging provider to send messages to the same service, while other providers can continue writing to the console or files. section 26.3

Listing 26.5 Adding a third-party logging provider to WebApplicationBuilder

WebApplicationBuilder builder = WebApplication.CreateBuilder(args);   #1
builder.Logging.AddFile();                                            #2
 
WebApplication app = builder.Build();
 
app.MapGet("/", () => "Hello world!");
 
app.Run();
#1 The WebApplicationBuilder configures the console and debug providers as normal.
#2 Adds the new file logging provider to the logger factory

Adds a third-party logging provider to WebApplicationBuilder with builder.Logging.AddFile(). section 26.3

Common destinations include:

Azure App Service, which provides centralized logging through its provider. section 26.3
Third-party aggregators such as elmah.io or Seq, added through NuGet logging providers. section 26.3

How ASP.NET Core in Action, 3e covers it

liveBook manning.com

Read ASP.NET Core in Action, 3e on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Kafka for ArchitectsA centralized logging system collects log records from multiple applications or services into a common system for storage, search, and analysis.
liveBook manning.com

Learn Docker in a Month of Lunches, Second EditionCentralized logging is a logging architecture in which logs from multiple applications or containers are collected and managed in a shared system.

Compare how 3 books explain 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.

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.