--- title: "File events" slug: "file-events-1" updated: 2026-09-11T11:11:55Z published: 2026-09-11T11:11:55Z canonical: "docs.trellix.com/file-events-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # File events The Event Streamer module has the ability to monitor and send events from various Windows server technologies. The module can monitor the logs from Microsoft DHCP server, DNS server, Exchange server, IIS, and Net logon log files from an active directory server. To add a file for monitoring: 1. Open the Event Streamer module policy configuration page. 2. Select the **File Events** tab. 3. Click the **ADD MONITORED FILE** button. The **Add File Stream** dialog box appears. ![Add_file_events.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-82828d1e-1a19-a18e-8c30-0f5bce01c83d(1).png?sv=2026-02-06&spr=https&st=2026-11-20T07%3A39%3A52Z&se=2026-11-20T08%3A39%3A52Z&sr=c&sp=r&sig=LgH3u1IDBBLuxqkeF3H44iKjvetNdsHr7QKv0Jp%2FFJI%3D) 4. Enter the following details for the file to be monitored: 1. **Display Name**: Name of the file provided to identify the file when it is displayed in the module policy UI. 2. **File Type**: The server log type to monitor and parse. Since each technology logs the data using different protocols, it is important to specify the correct file type. If the type is incorrect, the module will incorrectly parse the data and sends invalid data to the server. 3. **Location and Filename**: The full directory and name of file(s) to be monitored. To monitor all files with a specific extension, wildcards can be used (for example, *.log). To accommodate different system configurations, environment variables can be included as part of the directory paths (for example, SystemRoot). 4. Click **Save**. The module will start collecting events from these files. ### Note You might encounter Invalid or bad data displayed from file events on the destination server. To know more about the causes, see [Data displayed on the destination server](/docs/troubleshooting-1) :