--- title: "Alerts and packet capture management" slug: "alerts-and-packet-capture-management-1" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:27:13Z published: 2026-11-19T12:27:13Z canonical: "docs.trellix.com/alerts-and-packet-capture-management-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. # Alerts and packet capture management The Suricata Sensor sends events to the configured syslog server. The Sensor uses the event-based packet capture mechanism defined in the Snort rule to capture PCAP files and store the packet logs on the Sensor. ### Monitor alerts for Suricata Sensors Monitoring the alerts helps you identify threats and verify that your security policies are working effectively. You can monitor alerts in a Syslog server. Configure the syslog server settings in the Manager to receive rule-match events. Suricata Sensors support multiple syslog configurations. For more information, see [Configure a Syslog server](/network-and-platform/docs/configure-a-syslog-server-4). ### Event-based packet capture for Suricata Sensors Event-based packet capture allows you to capture network traffic data based on specific rule triggers. You can configure the event-based packet capture by modifying the `timemachine` parameters in the Suricata YAML file. ```plaintext timemachine: # Enable the time machine feature to buffer packets on a best-effort basis. # The system flushes these packets to a pcap file when an alert is raised.  enabled: yes # Use the zerolenpkt-enabled flag to capture initial protocol handshake messages.  zerolenpkt-enabled: yes  # Specify the maximum memory per thread for the time machine.  # The memory per thread is the sum of the max-packet-size  # multiplied by the count of heap spaces for each heap within a thread.  max-memory: 512mb  # Specify the amount of pre-allocated heap space to generate.  # You can override this value for each heap.  heap-prealloc-count: 5000 ``` When a rule includes the `ebc pcap` keyword in the metatdata, the Sensor generates a packet capture file that you can fetch and store in the Manager database for analysis. This process provides the detailed visibility needed to investigate security incidents. **Example**: ```plaintext alert http $EXTERNAL_NET any -> $HTTP_SERVERS any (msg:"GPL EXPLOIT CodeRed v2 root.exe access"; flow:established,to_server; http.uri; content:"/root.exe"; nocase; reference:url,www.cert.org/advisories/CA-2001-19.html; classtype:web-application-attack; sid:2101256; rev:12; metadata:created_at 2010_09_23, updated_at 2024_03_08, ebc pcap;) ``` The Manager supports downloading packet logs for specific alerts via API. - Storage on the Sensor: The Sensor stores PCAP files locally and embeds the corresponding **alertid** in the file name for mapping. - Transfer to the Manager: The Manager runs a scheduler every five minutes to fetch PCAP files via TFTP. You can monitor the system status using `show suricata stats all` command.