Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data

Update timeline

1. investigating Oct 27, 2026, 02:40 PM UTC

   We are aware of an issue causing ingested syslogs content to appear empty for some customers. This is only affecting ActiveGates that have updated to version 1.347. Our teams are actively investigating. We will provide the next status update within two hours. We apologize for the disruption and appreciate your patience as we work to resolve the issue.

2. identified Oct 27, 2026, 04:53 PM UTC

   We have identified the issue causing ingested syslog content to appear empty for a small subset of customers using ActiveGate version 1.347 and are actively working on a fix. We advise customers not to downgrade that version of ActiveGate, as doing so will not resolve this issue. If you believe you are affected, please contact your support team for a workaround to use until the fix has been implemented. We will provide the next status update within two hours.

3. identified Oct 27, 2026, 05:43 PM UTC

   We have identified the cause of an issue in ActiveGate version 1.347 that results in ingested syslog content appearing empty. The impact is limited to a small subset of customers who ingest non-standard syslog formats, and our engineering team is actively developing a fix. Please note that downgrading ActiveGate will not resolve this issue, so we recommend remaining on the current version. If you believe you are affected, a workaround is available to use until the fix has been implemented. Please review the steps in our Community post: https://community.dynatrace.com/t/workaround-syslogs-ingestion-via-activegate-version-1-347-presenting-empty-data/57278 If you have any difficulty applying the workaround, please open a support case and our team will assist you. We will provide the next update within the next 24 hours, or sooner once the fix has been implemented.

4. monitoring Oct 28, 2026, 04:54 PM UTC

   A fix has been implemented for the issue in ActiveGate version 1.347 that caused ingested syslog content to appear empty. This issue affected a small subset of customers who ingest non-standard syslog formats. Our team will continue to closely monitor the fix to ensure ongoing stability. Customers who implemented the previously provided workaround may now revert that change. Leaving the workaround in place will not have an adverse impact. If you continue to experience any issues, please open a support case or contact your account team, and we will assist you promptly. We will provide an update once we have concluded our monitoring, or sooner should there be any developments. We appreciate your patience and continued partnership.