Golive instabilities

Summary

Golive instabilities

The issue appears to be successfully addressed. It stemmed from contention within our system responsible for communication with Jira instances. To remedy this, we have refined the initiation of calls to Jira, reducing their frequency. Additionally, we have augmented the pool size of the system overseeing the contention, enhancing its capacity to handle tasks effectively.

• Started

  Jan 30, 2024 · 4:24 PM

• Resolved

  Feb 1, 2024 · 2:03 PM

• Duration

  1d 21h 38m

• Severity

  Minor

• ◐

  Investigating

  Jan 30 · 4:24 PM Apwide

  Apwide Golive is currently experiencing instabilities. Our teams are working to identify the causes.

• ◐

  Investigating

  Jan 30 · 10:51 PM Apwide

  Platform is stable for 5 hours but analysis to identify the root cause is still ongoing.

• ◆

  Identified

  Jan 31 · 8:29 AM Apwide

  A potential root cause has been pinpointed, and a configuration workaround has been implemented in the production environment. We are actively monitoring its impact. Concurrently, efforts are underway to develop a permanent fix.

• ◉

  Monitoring

  Feb 1 · 10:09 AM Apwide

  A fix has been implemented and we are monitoring the results.

• ✓

  Resolved

  Feb 1 · 2:03 PM Apwide

  The issue appears to be successfully addressed. It stemmed from contention within our system responsible for communication with Jira instances. To remedy this, we have refined the initiation of calls to Jira, reducing their frequency. Additionally, we have augmented the pool size of the system overseeing the contention, enhancing its capacity to handle tasks effectively.