[MAGNOLIA-7764] Notification when running into potential delays of scheduled publishing Created: 03/Apr/20  Updated: 22/Apr/20

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Annick Boehler Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

At the end of August, high CPU usage was detected in a customer project. This lead to some delays to schedule publishing functionality.

To detect this possible delays in scheduled publishing they would like to set up notification at a given threshold.

Facts:

  • Checking with Ervin and currently the value can have peaks up to 60% per public
  • During the high CPU usage time, this peak raised up to 160% (across 3 publics)
  • High peaks on CPU might not lead to delays of scheduled publishing but it could have potential.

If you would see another way to notify possible delays on scheduled publishing, we will welcome the different approach.

Aim: How can we foreseen or mitigate “delays” on schedule publishing

Details of existing investigation in linked tickets:


Generated at Mon Feb 12 04:26:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.