Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data

What to do

• Check whether your product depends on Dynatrace. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-28 20:33 UTC and 2026-10-28 20:33 UTC may need a replay.

• Subscribe to Dynatrace's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=dynatrace works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

Identified - We have identified the cause of an issue in ActiveGate version 1.

Updates from Dynatrace 1

1. resolvedOct 28, 2026, 8:33 PM UTC

   October 27, 2026 2:40PM UTC Investigating - 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. October 27, 2026 4:53PM UTC Identified - 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. This issue only affects customers who ingest non-standard syslogs. 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. October 27, 2026 5:43PM UTC Identified - 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. October 28, 2026 4:54PM UTC Monitoring - 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. October 28, 2026 8:33PM UTC Resolved - The fix for the issue in ActiveGate version 1.347, which caused ingested syslog content to appear empty for a small subset of customers using non-standard syslog formats, has proven stable following our monitoring period. As a result, we are now resolving this issue. Customers who implemented the previously provided workaround may revert that change at their convenience. 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.   Thank you for your patience while we addressed this issue. We greatly value your continued partnership.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.