Impact:
Harness custom dashboards were intermittently inaccessible during the time of the incident.
Root Cause:
Custom Dashboards microservice in the harness cluster of services had experienced a server overloaded with requests causing a CPU spike resulting in a crash and a restart and due to the high volume of requests the UI was inaccessible.
Timeline:
Time Event May 16 at 12:32 PM PST Internal team noticed slowness in custom dashboards May 16 at 12:32 PM PST Internal call was initiated and engineering started triaging May 16 at 12:41 PM PST Functionality returned back to normal after a pod restart
Action items:
Adopting the Gunicorn server to handle more requests per second and added resiliency