--- title: "Log aggregation system configuration for Helix Enterprise" slug: "log-aggregation-system-configuration-for-helix-enterprise" tags: ["Reference", "Helix Enterprise", "Sec Ops and Analytics"] updated: 2026-09-14T13:34:39Z published: 2026-09-14T13:34:39Z canonical: "docs.trellix.com/log-aggregation-system-configuration-for-helix-enterprise" stale: true --- > ## 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. # Log aggregation system configuration for Helix Enterprise If you have already implemented an enterprise log management system, you will likely be able to leverage those systems to send logs into Helix Enterprise. The following are required to ensure Helix Enterprise effectively parses the log data from these systems: - Do not alter the original message. - Preserve the original source IP address (typically this spoofing requires UDP forwarding vs. TCP). - Preserve the original timestamp. - Preserve the original program name. - Preserve the original message format. For examples of existing aggregations systems from which customers have successfully forwarded messages and logs, see [Data Source Configuration](/network-and-platform/docs/data-source-configuration).