Dynatrace: Logs and Metrics Ingestion possibly delayed in East-US (Virginia)
Affected components: Dynatrace Product
Timeline of updates
- identifiedEdited
Data gaps may possibly be observed in Azure EAST US (Virginia) due to delays in log and metrics ingestions. No data loss at this stage. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may cause. We will provide another update within the next hour, or sooner if additional information becomes available.
- monitoring
We have applied mitigation efforts for the issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, and entities. We are now seeing data flow as expected for the affected data types. Our teams will continue to monitor the service closely to confirm ongoing stability and ensure customer impact remains mitigated. We will provide an update in the next two hours or sooner.
- monitoring
We have applied mitigation efforts for the issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, and entities. We are now seeing data flow as expected for the affected data types. There was no data lost stemming from this incident. Our teams will continue to monitor the service closely to confirm ongoing stability and ensure customer impact remains mitigated. We will provide an update in the next two hours or sooner.
Changes Rewindex caught on this incident
- Incident silently edited: Logs and Metrics Ingestion possibly delayed in East-US (Virginia)
- Incident updated: Logs and Metrics Ingestion possibly delayed in East-US (Virginia)
- Incident updated: Logs and Metrics Ingestion possibly delayed in East-US (Virginia)
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.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on dynatrace.status.io (opens in new tab).