Collect Windows event logs

Implementation

The Windows Event Log API and Event Logging API are provided in Windows operating systems to record event logs. The Windows Event Log API supersedes the Event Logging API in the Windows Vista operating system or later. Logtail plug-ins automatically select an API based on the operating system to collect Windows event logs. Windows Event Log is preferred.

As shown in the following figure, the publish-subscribe model is used to collect Windows event logs. An application or kernel publishes event logs to the specified channel, such as the application, security, or system channel. Logtail uses this plug-in to call the Windows Event Log API or Event Logging API to subscribe to these channels. In this way, Logtail continuously collects event logs and sends the logs to Log Service.

Logtail allows you to collect logs from multiple channels at the same time. For example, you can collect logs from the application channel and system channel.

View channel information

You can view the information about channels in the Event Viewer of a Windows server.

1. Click Start.
2. Search and click Event Viewer. The Event Viewer window appears.
3. In the left-side navigation pane, expand Windows Logs.
4. View the full names of channels.
   Right-click the target channel under Windows Logs and select Properties. On the window that appears, you can view the full name of the channel. The following full names of common channels are displayed under Windows Logs.

   • Application
   • Security
   • Setup
   • System
5. View the information about channels.
   Click the target channel under Windows Logs. On the window that appears, you can view the level, date and time, source, and ID of each event.

   You can set filtering conditions in Logtail configurations based on the preceding fields.

   

Procedure

1. Log on to the Log Service console.
2. In the Import Data section, select Custom Data Plug-in.
3. In the Specify Logstore step, select the target project and Logstore, and click Next.
   You can also click Create Now to create a project and a Logstore. For more information, see Step 1: Create a project and a Logstore.
4. In the Create Machine Group step, create a machine group.
   • If a machine group is available, click Using Existing Machine Groups.
   • If no machine group is available, perform the following steps. The following steps take ECS instances as an example to describe how to create a machine group:
     1. Install Logtail on ECS instances. For more information, see Install Logtail on ECS instances.

        If Logtail is installed on the ECS instances, click Complete Installation.

        Note If you need to collect logs from user-created clusters or servers of third-party cloud service providers, you must install Logtail on these servers. For more information, see Install Logtail in Windows.
     2. After the installation is completed, click Complete Installation.
     3. On the page that appears, set relevant parameters for the machine group. For more information, see Create an IP address-based machine group or Create a custom ID-based machine group.
5. In the Machine Group Settings step, apply the configurations to the machine group.
   Select the created machine group and move the group from Source Server Groups to Applied Server Groups.
6. In the Specify Data Source step, set the Config Name and Plug-in Config parameters.
   • inputs: Required. The Logtail configurations for log collection.
     Note You can configure only one type of data source in the inputs field.
   • processors: Optional. The Logtail configurations for data processing. You can configure one or more processing methods in the processors field. For more information, see Process data.

   The following example shows how to collect logs from the Application and System channels. The value of the IgnoreOlder parameter is set to 259200 (three days) to avoid collecting excessive logs.

   {
       "inputs": [
           {
               "type": "service_wineventlog",
               "detail": {
                   "Name": "Application",
                   "IgnoreOlder": 259200
               }
           },
           {
               "type": "service_wineventlog",
               "detail": {
                   "Name": "System",
                   "IgnoreOlder": 259200
               }
           }
       ]
   }

   Parameter	Type	Required	Description
   type	String	Yes	The type of the data source. Set the value to service_wineventlog.
   Name	String	Yes	The name of the channel to which the collected event logs belong. You can specify only one channel. Default value: Application. This value indicates that event logs are collected from the application channel. For information about how to obtain the full name of a channel, see step 4.
   IgnoreOlder	Uint	No	Filters logs by event time. This parameter indicates an offset of the time from which event logs are collected. Unit: seconds. Logs that are generated earlier than the specified time are not collected. Examples: 3600: Logs that are generated 1 hour before the start time of collection are not collected. 14400: Logs that are generated 4 hours before the start time of collection are not collected. Default value: null. This value indicates that event logs are not filtered by time during log collection. Note This parameter takes effect only when logs are collected for the first time. Logtail records checkpoints during log collection. This mechanism avoids repeated log collection.
   Level	String	No	Filters logs by severity. Default value: information, warning, error, critical. This value indicates that logs of all severity levels except verbose are collected. Available severity levels include information, warning, error, critical, and verbose. You can specify multiple severity levels for the parameter by separating these severity levels with commas (,). Note This parameter is available only when you use Logtail plug-ins to call the Windows Event Log API for log collection.
   EventID	String	No	Filters logs by event ID. You can specify one or more IDs for positive filtering, or for negative filtering. Default value: null. This value indicates that all event logs are collected. Examples: 1-200: Only the logs whose event IDs are 1 to 200 are collected. 20: Only the logs whose event ID is 20 are collected. -100: All logs are collected, except the logs whose event ID is 100. 1-200,-100: The logs whose event IDs are 1 to 99 or 101 to 200 are collected. You can separate multiple IDs or ID ranges with commas (,). Note This parameter is available only when you use Logtail plug-ins to call the Windows Event Log API for log collection.
   Provider	String array	No	Filters logs by event source. For example, the value of ["App1", "App2"] specifies that only event logs from the sources named App1 and App2 are collected. Default value: null. This value indicates that event logs from all sources are collected. Note This parameter is available only when you use Logtail plug-ins to call the Windows Event Log API for log collection.
   IgnoreZeroValue	Boolean	No	Filters unavailable fields. Some fields may be unavailable in a log entry. You can set the value of the parameter based on the data type of an unavailable field. For example, set the value to 0 if the data type of an unavailable field is integer. Default value: false. This value indicates that unavailable fields are not filtered.

7. In the Configure Query and Analysis step, configure the indexes.
   Indexes are configured by default. You can re-configure the indexes based on your business requirements. For more information, see Enable and configure the index feature for a Logstore.

   Note

   • You must configure Full Text Index or Field Search. If you configure both of them, the settings of Field Search are applied.
   • If the data type of index is long or double, the Case Sensitive and Delimiter settings are unavailable.