Internal Monitoring Data Delay
Jul 1, 15:39 UTCJul 1, 20:23 UTC
Duration
4h 44m
Impact
Minor
Root cause
Not disclosed
Elastic, 90 days
22 incidents
Affected
Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastusAzure Virginia (azure-eastus2) - Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Azure Washington (azure-westus2) - Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Azure Virginia (azure-eastus) - Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus
Final update
This issue has been resolved.
Timeline
- Resolved · Jul 1, 20:23 UTC
This issue has been resolved.
- Monitoring · Jul 1, 19:50 UTC
The system has recovered and we are continuing to monitor the situation.
- Identified · Jul 1, 16:50 UTC
We have identified the issue and implemented a fix. We are seeing signs of system recovery and are continuing to monitor the situation closely.
- Investigating · Jul 1, 15:39 UTC
We're experiencing a monitoring data delay affecting a limited number of Azure regions. Elastic Cloud's internal metrics for these regions are being ingested more slowly than usual. What you may notice: Deployment metrics and instance utilization data may not appear in the Elastic Cloud UI for Hosted Deployments and Serverless Projects in affected regions. What's not affected: Your deployments and projects are running normally. Data ingestion and all functionality remain unimpacted besides lacking some monitoring data on the Elastic Cloud UI. We're actively investigating the root cause and will provide an update within the next 2 hours.
More from Elastic
Full historymOLTP PrivateLink connectivity issuelasted 13h 28mElastic Support Portal is unavailablelasted 2h 29m403 error when trying to access Autoops in newly created serverless projectslasted 9h 31mElastic Cloud scaling issues in Azurelasted 6h 57mDegraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)lasted 15h 3mDelayed or Unavailable project operation in GCP us-central1lasted 8h 12m