An issue was found in the Elasticsearch production database, classified as a SEV2 incident, potentially affecting customers. JP Cheung reported the incident after receiving an alert via Slack and is currently serving as the Commander overseeing the response efforts. Steps taken include ensuring role assignments and updating the Rootly summary, though no one has been assigned to check the access cluster health API yet.
- Severity: SEV2 - Services: elasticsearch-prod - @Incident Types: Cloud, Customer Facing - Root Cause Analysis: What caused this incident