Incidentsby GlyphAutoOps monitoring data not ingested for subset of deployments
Jul 21, 13:45 UTCJul 21, 14:21 UTC
Duration
35m
Impact
Major
Root cause
Not disclosed
Elastic, 90 days
22 incidents
Affected
AutoOpsGlobal services - AutoOps
Final update
This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Timeline
- Resolved · Jul 21, 14:21 UTC
This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
- Identified · Jul 21, 13:45 UTC
RESOLVED - Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe. Note this incident has already been resolved, and is being posted retroactively.
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