Welcome to the updated version of the dashboard (1.5)
Version 1.5
A button has been added for event planning. The event will be announced through a banner on top of the dashboard, the day the event takes place.
Version 1.3
A debug button has been added to the overnight history popup screen. This debug info is useful for determining which blocks were missing, why the End-Of-Overnight report is still not finished, etc.
Version 1.2
New columns have been added showing the max timings between each step, the overtime and the offsets for creating OPSgenie alerts.
The number in the column called 'Alert', shows the number of overtime minutes a step can stay in, before a P3 OPSgenie alert is created.
The same applies to the column called 'Ring'. This one shows the number of minutes before creating a P2 OPSgenie alert.
The pop-up screen showing the details of the overnight, will no longer dissapear when the main screen refreshes.
What is the difference between an OPSgenie P2 or P3 alert? P3: an alert is created in the OPSgenie dashboard. OPSgenie starts notifying (ringing,SMS) the 2LSB operator after 8:00 (CET). As soon as the operator ack's the event, a Jira ticket is created. P2: an alert is created in the OPSgenie dashboard. OPSgenie starts notifying (ringing,SMS) the 2LSB operator after 6:00 (CET). As soon as the operator ack's the event, a Jira ticket is created.
Remark: an error message will immediately create a P1 alert and Jira ticket, which means that the 'Alert' and 'Ring' timings are ignored. OPSgenie starts notifying (ringing,SMS) the 2LSB operator only after 6:00 (CET)
Before you decide to send this mail, please check first the errors that occurred and the content of the 'Overnight Summary' Excel.
Please beware that when you press the 'send' button, the mail itself will be queued for sending. This can take some extra minutes.
Pressing the SUPPRESS button will suppress all OPSGenie alerts for the selected customer.
Beware that you understand the risks in doing this because no Jira tickets will be created, nor will the 2LSB team get activated.
For audit reasons you are asked to specify your name and a reason why you want to enable the SUPPRESS function.
This data will also be mailed automatically to the 2LSB team and the CSM.
Your name:
Reason for enabling the SUPPRESS function:
Note: HTML code will be stripped away. Only the <BR> tag is allowed for creating a newline.
Pressing the SUPPRESS button will suppress all OPSGenie alerts for the SaaS clients shown in the middle block.
Beware that you understand the risks in doing this because no Jira tickets will be created, nor will the 2LSB team get activated.
For audit reasons you are asked to specify your name and a reason why you want to enable the SUPPRESS function.
This data will also be mailed automatically to the 2LSB team and the CSM.
Your name:
Reason for enabling the SUPPRESS function:
Note: HTML code will be stripped away. Only the <BR> tag is allowed for creating a newline.
Pressing the DISABLE SUPPRESSION button will stop suppressing all OPSGenie alerts for the selected customer.
Below you find the name of the person who activated the suppression mode and the reason why it was needed.
Suppressed by:
Suppression reason:
Pressing the DISABLE SUPPRESSION button will stop suppressing all OPSGenie alerts for the SaaS clients shown in the middle block.
1. Choose one of the message types below.
2. If needed, modify the suggested title and message text.
3. To send the overnight e-mail to '', press the SEND button.
Title
Message
Note: HTML code will be stripped away. Only the <BR> tag is allowed for creating a newline.
Beware that not all extracted files have been received at this moment. Invoking a forced mail sending will ONLY mail those files that have been received up till now.
Any other files that will arrive later, will not be sent anymore (unless you manually relink & resend them through the Overnight Configuration panel on the portal in Admin mode).
Please beware that when you press the 'send' button, the mail itself will be queued for sending. This can take some extra minutes.
Mention below if you are going to work on this problem so that your colleagues know that this problem is under investigation:
Max : max allowed duration of block step. A longer duration is called Overtime (see Delta column) Alert : delay before P3 OPSgenie alert is created (snoozed until 8:00 CET) Ring : delay before P2 OPSgenie alert is created + operator is called instantly (snoozed until 6:00 CET)
Note: at this moment the balance dates for the overnights marked with , are not reflecting the correct balance date.
We are looking to investigate if the different overnight cycles can be adapted so that it will be reflecting the correct balance date.