|
@@ -0,0 +1,53 @@
|
|
|
+<!--startmeta
|
|
|
+custom_edit_url: "https://github.com/netdata/netdata/edit/master/integrations/logs/integrations/windows_event_logs.md"
|
|
|
+meta_yaml: "https://github.com/netdata/netdata/edit/master/integrations/logs/metadata.yaml"
|
|
|
+sidebar_label: "Windows Event Logs"
|
|
|
+learn_status: "Published"
|
|
|
+learn_rel_path: "Logs"
|
|
|
+message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE LOGS' metadata.yaml FILE"
|
|
|
+endmeta-->
|
|
|
+
|
|
|
+# Windows Event Logs
|
|
|
+
|
|
|
+
|
|
|
+<img src="https://netdata.cloud/img/windows.svg" width="150"/>
|
|
|
+
|
|
|
+
|
|
|
+The Windows Events plugin by Netdata makes viewing, exploring and analyzing Windows Events simple and
|
|
|
+efficient.
|
|
|
+
|
|
|
+The plugin automatically detects all the available channels and offers a list of "Event Channels".
|
|
|
+
|
|
|
+By default, it aggregates events from all event channels, providing a unified view of all events.
|
|
|
+
|
|
|
+
|
|
|
+<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />
|
|
|
+
|
|
|
+## Visualization
|
|
|
+
|
|
|
+You can start exploring Windows event logs on the "Logs" tab of the Netdata UI.
|
|
|
+
|
|
|
+
|
|
|
+## Key features
|
|
|
+
|
|
|
+- Supports **Windows Event Logs (WEL)**.
|
|
|
+- Supports **Event Tracing for Windows (ETW)** and **TraceLogging (TL)**, when events are routed to Event Log.
|
|
|
+- Allows filtering on all System Events fields.
|
|
|
+- Allows **full text search** (`grep`) on all System and User fields.
|
|
|
+- Provides a **histogram** for log entries over time, with a break down per field-value, for any System Event field and any
|
|
|
+ time-frame.
|
|
|
+- Supports coloring log entries based on severity.
|
|
|
+- In PLAY mode it "tails" all the Events, showing new log entries immediately after they are received.
|
|
|
+
|
|
|
+
|
|
|
+## Setup
|
|
|
+
|
|
|
+## Prerequisites
|
|
|
+
|
|
|
+- Netdata Cloud paid subscription
|
|
|
+
|
|
|
+
|
|
|
+## Configuration
|
|
|
+
|
|
|
+There is no configuration needed for this integration.
|
|
|
+
|