Logger
A logger is a software component or interface that records or emits runtime information, such as diagnostic messages, events, or metrics.
Learn Go with Pocket-Sized Projects
A logger is a software component that records application messages, typically with severity levels and formatted output.
- How it is used
- Records application events at selectable levels so debugging and routine messages need not rely on unconditional prints.
- How deep it goes
- Works through an exported API, threshold filtering, shared formatting, configurable output, and tests; leaves write-error handling unresolved.
- Examples
- Uses a three-level pocketlog implementation, a custom test writer, and expected newline-separated output at different thresholds.
- What you can do after
- Build it from scratch as a configurable Go logger and test its filtering and written output.
Read how Learn Go with Pocket-Sized Projects explains Logger →
ASP.NET Core in Action, 3e
ILogger is a .NET logging abstraction whose methods record application diagnostic messages through configured providers.
- How it is used
- Records diagnostic events so applications can diagnose errors and control logging verbosity across development and production.
- How deep it goes
- Explains injection, providers, levels, categories, templates, and structured values, while deferring detailed filtering and provider configuration.
- Examples
- Uses a Razor Page recipe count, console provider setup, custom categories, and a generated LoggerMessage method.
- What you can do after
- Apply it via ASP.NET Core dependency injection to write categorized, leveled, structured messages through configured providers.
Python How-To
A logger is an object in a logging system that creates log records and applies a severity threshold before forwarding them to handlers.
- How it is used
- Records application events through a reusable module logger, with handlers directing records to files or the console.
- How deep it goes
- Works through logger retrieval, handler attachment, severity filtering, and duplicate-handler pitfalls without detailing less-common handler types.
- Examples
- Uses a task-removal warning saved to a log file and messages at five severity levels to show filtering.
- What you can do after
- Operate/configure it to reuse a module logger, select event severity, and route records to persistent or live outputs.
Building Web APIs with ASP.NET Core
ILogger is a .NET logging abstraction for writing categorized diagnostic messages.
- How it is used
- Records categorized application events and activities through logging providers.
- How deep it goes
- Explains generic categories, dependency injection, log levels, event IDs, and message templates through controller examples.
- Examples
- Uses a board-game controller log entry, event ID constants, named placeholders, and Output-window results.
- What you can do after
- Apply it via ASP.NET Core dependency injection to record categorized controller events and inspect their output.
Read how Building Web APIs with ASP.NET Core explains Logger →
Troubleshooting Java, Second Edition
A logger is a Log4j component or object that accepts application messages at specified severity levels.
- How it is used
- Routes application events through severity filtering during behavior auditing and execution investigation.
- How deep it goes
- Explains creation, severity methods, configuration, appenders, and formatters, but does not descend into framework internals.
- Examples
- Uses a StringDigitExtractor, Log4j API calls, log4j2.xml configuration, console output, and adjustable info/debug thresholds.
- What you can do after
- Apply it via Log4j to emit severity-specific messages and configure their selection, destination, and formatting.
Read how Troubleshooting Java, Second Edition explains Logger →
Related concepts
- dependency injectionused by · Dependency injection is a software design technique in which a component receives its dependencies from outside rather than creating or locating them internally.
- ILoggerFactoryproduced by · ILoggerFactory is a .NET logging abstraction that creates category-specific loggers and manages logging providers.
- logging levelconfigured by · A logging level is a severity or verbosity classification or setting that determines which log messages a logging system processes, emits, or retains.
- monitoringuses · 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.
- ILoggerProviderused by · ILoggerProvider is a .NET logging interface that creates logger instances associated with a logging destination or implementation.
- log categoryconfigures · A log category is a named identifier for the component or source of log messages that enables source-specific filtering and configuration.
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.