The Logging System
The documentation is still a work in progress. Some pages still contain but a placeholder, filling in the content as fast as I an make myself write it.
Synopsis
The logging system enables maximum flexibility when logging for minimal complexity to use. It supports logging in different formats to a variety of logging services. Its asynchronous nature prevents impact on code performance while being runspace-safe to use.
Key Features / Benefits
- Log to file, eventlog, Azure Log Analytics, Splunk, Graylog or SQL with out-of-the-box-tools
- Simple to use: Get started in less than 5 minutes
- Extensible with custom logging logic
- Configurable logging at script, process, user or machine level
- Enable scripts to integrate into existing logging, without code-change
- Runspace-Safe: Logging from multiple runspaces in parallel without conflict
- Rich log data for both debugging and auditing
- Automatic debug log
Core Concepts
Quick Start Guides
Logging To …
A quick refence list on how to log to the built-in Logging Providers:
- … the debug log
- … a logfile
- … the Windows Eventlog
- … Azure Log Analytics
- … Splunk
- … Graylog
- … SQL
- … Console
Basics
- Writing Messages
- Troubleshooting
- Logging Providers
- In-Memory debug log
- Message Levels
- Multilingual Messages
- Message Configuration Settings
- Tuning the Message display style
Logging Providers
The full reference documentation for each built-in Logging Provider
- The FileSystem Provider
- The LogFile Provider
- The Eventlog Provider
- The Azure Log Analytics Provider
- The GELF Provider
- The Splunk Provider
- The SQL Provider
- The Console Provider
Conference Recordings
Advanced
- Writing Custom Logging Providers
- The Logging Sequence
- Debugging Logging Providers
- Message Policies
- Cmdlets & Logging
- Logging Provider Generations
- Filtering by Runspace