Dynatrace: Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data
Affected components: Dynatrace Product
Timeline of updates
- 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.
- identifiedEdited
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.
- 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 (opens in new tab) 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.
- 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.
- 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.
Changes Rewindex caught on this incident
- Incident updated: Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data
- Incident silently edited: Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data
- Incident updated: Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data
- Incident updated: Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data
- Incident updated: Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
193dd03acdac05ce…Version 2 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
4bc599b2ebb3edc0…Version 3 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
719eea3d9c683c39…Version 4 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
e0c454bccf837f4a…Version 5 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e9c0d802b46648a6…Version 6 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
28c35e1e2847aac9…
Impact, status and times are the vendor’s own, as last archived. View on dynatrace.status.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Dynatrace, started 2026-10-27 14:40 UTC, resolved after 30 h, 5 update(s); edited after publishing.
- Title
- Syslogs Ingested via ActiveGate version 1.347 Presenting Empty Data
- Vendor
- Dynatrace
- Date
- URL
- https://rewindex.com/company/dynatrace/incidents/6ae0b7fa3e42aa05ed5adde8
Dynatrace profileRecent Dynatrace incidentsAll outages on October 27, 2026Dynatrace in October 2026MarkdownJSON