- Overview
- Module Description - What is the windows_eventlog module?
- Setup - The basics of getting started with windows_eventlog
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- License
- Development - Guide for contributing to the module
Puppet module for managing windows event logs
The purpose of this module is to manage each of the Windows event logs, including the size, rotation and retention
- Sets registry keys to manage the event log configuration
Manage the size of the Application log:
windows_eventlog { 'Application':
log_path => '%SystemRoot%\system32\winevt\Logs\Application.evtx',
log_size => 2048,
max_log_policy => 'overwrite',
}
Manage several custom logs under C:\Logs:
windows_eventlog { ['Custom1', 'Custom2', 'Custom3']:
log_path_template => 'C:\Logs\%%NAME%%.evtx',
}
The primary definition of this module. Manages the size and rotation policy of Windows event logs
Parameters within windows_eventlog
:
(Optional) The path to the log file that you want to manage.
The max size of the log file in bytes. Defaults to 1028
.
The retention policy for the log. Defaults to 'overwrite
'.
(Optional) A template for log_path
, where "%%NAME%%
" will be replaced with
the log name. Defaults to '%SystemRoot%\\system32\\winevt\\Logs\\%%NAME%%.evtx
'.
windows_eventlog
: Manages the size and rotation policy of a Windows event log
This module is tested on the following platforms:
- Windows 2008 R2
It is tested with the OSS version of Puppet only.
This codebase is licensed under the Apache2.0 licensing, however due to the nature of the codebase the open source dependencies may also use a combination of AGPL, BSD-2, BSD-3, GPL2.0, LGPL, MIT and MPL Licensing.
Please read CONTRIBUTING.md for full details on contributing to this project.
This module was previously maintained by Vox Pupuli. It was migrated to Puppet/Perforce in 2023.