Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Service Level Target - ROD performance index"

From EGIWiki
Jump to navigation Jump to search
 
(24 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}
{{Template:Op menubar}} {{TOC_right}}  
{{Template:GO menubar}} {{TOC_right}}  


[[Category:Grid Oversight]]
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;"
[[Category:Service_Level_Management]]
| style="padding-right: 15px; padding-left: 15px;" |
|[[File:Alert.png]] This article is '''Deprecated''' and should no longer be used, but is still available for reasons of reference.
|}


The ROD performance index (<span lang="en" class="short_text" id="result_box"><span class="hps">formerly known as ROD&nbsp;OLA metric</span></span>) was introcuded to track the level of Grid Oversight service delivered by Operations Centres according to [https://documents.egi.eu/secure/ShowDocument?docid=463 Resource Provider OLA].  
The ROD performance index (<span lang="en" class="short_text" id="result_box"><span class="hps">formerly known as ROD&nbsp;OLA metric</span></span>) was introcuded to track the level of Grid Oversight service delivered by Operations Centres according to [https://documents.egi.eu/secure/ShowDocument?docid=463 Resource Provider OLA].  


The index was accepted during Technical Forum 2011 in Lyon and is available on [https://operations-portal.in2p3.fr/dashboard/rodOlaMetrics EGI&nbsp;Operations Portal].  
The index was accepted during Technical Forum 2011 in Lyon and is available on [https://operations-portal.egi.eu EGI&nbsp;Operations Portal]. (choose Metrics tab).
 
= Definition  =
 
'''ROD performance index''' is the sum of:


= Definition  =
'''ROD performance index''' is the sum of:
*No. of ticket expired<sup>*</sup> <span lang="en" id="result_box" class="short_text"><span class="hps"> in the operations dashboard daily</span></span>  
*No. of ticket expired<sup>*</sup> <span lang="en" id="result_box" class="short_text"><span class="hps"> in the operations dashboard daily</span></span>  
*No. alarms older than 72h <span lang="en" id="result_box" class="short_text"><span class="hps"> appearing</span></span><span lang="en" id="result_box" class="short_text"><span class="hps">in operations dashboard daily</span></span>
*No. alarms older than 72h <span lang="en" id="result_box" class="short_text"><span class="hps"> appearing</span></span><span lang="en" id="result_box" class="short_text"><span class="hps">in operations dashboard daily</span></span>


<span lang="en" class="short_text">
<span lang="en" class="short_text">
</span>  
</span> A ticket in counted as '''expired''' in the [https://operations-portal.egi.eu Operations Portal dashboard] if the "Expiration date" is set at a time in the past. The "Expiration date" field is set according to [https://wiki.egi.eu/wiki/PROC01 | escalation procedure], but can be freely changed by ROD. It refers to the date when the status of issue should be checked next time.  
A ticket in counted as '''expired''' in the [https://operations-portal.egi.eu/dashboard Operations Portal dashboard] if the "Expiration date" is set at a time in the past. The "Expiration date" field is set according to [[PROC01 |escalation procedure]], but can be freely changed by ROD. It refers to the date when the status of issue should be checked next time.


The ROD performance index is calculated monthly from the data gathered by EGI Operations Portal. It does not take into account weekends.
The ROD performance index is calculated monthly from the data gathered by EGI Operations Portal. It does not take into account weekends.  


= Threshold =
= Threshold =
The maximum value of the index must be 10. Above this value ROD teams has to provide explanation and provide a plan of improvement of the oversight service.


= <span class="mw-headline">Performance reports</span><br>  =
The maximum value of the index must be 10. Above this value ROD teams has to provide explanation and provide a plan of improvement of the oversight service.


Performance reports can be found [https://documents.egi.eu/document/1089 here]
<br>


= Recalculation procedure in case of intervention on the NGI SAM or the operations dashboard  =
= Recalculation procedure in case of intervention on the NGI SAM or the operations dashboard  =
Line 31: Line 32:
'''Prerequisite''':  
'''Prerequisite''':  


#In case of problems with synchronization between regional operations dashboard the Resource infrastructure Provider should create a GGUS ticket to Operations Portal team.
#In case of problems with the regional SAM, Resource infrastructure Provider should create a GGUS ticket to SAM team.  
#In case of problems with the regional SAM, Resource infrastructure Provider should create a GGUS ticket to SAM team.  
#In case of work carried out on regional SAM or operations dashboard the Resource infrastructure Provider should declare downtime in GOC DB.
#In case of work carried out on regional SAM the Resource infrastructure Provider should declare downtime in GOC DB.


'''Procedure steps:'''  
'''Procedure steps:'''  


#When an Operations Centre get a ticket from COD about ROD performance, the Operations Centre should provide GGUS ticket or a link to SAM or the oeprations dashboard downtime page in GOC DB.  
#When an Operations Centre get a ticket from EGI Operations about ROD performance, the Operations Centre should provide GGUS ticket or a link to SAM or the operations dashboard downtime page in GOC DB.  
#*If ROD performance index is below 10 items, NGI can create a GGUS ticket to COD asking for recalculation
#*If ROD performance index is below 10 items, NGI can create a GGUS ticket to EGI Operations asking for recalculation  
#Based on GGUS trouble tickets referenced in prerequisites, or on the GGUS ticket opened by the Operations Centre to MyEGI requesting for A/R recualculation, or GOC DB service downtime entry, COD, knowing when the problem occurred,<br>can remove the metrics items for given days from final report pdf.
#Based on GGUS trouble tickets referenced in prerequisites, or on the GGUS ticket opened by the Operations Centre to MyEGI requesting for A/R recalculation, or GOC DB service downtime entry, EGI Operations, knowing when the problem occurred,<br>can remove the metrics items for given days from final report pdf.
 
= <span class="mw-headline">Performance reports</span><br>  =
 
'''Since October 2014 reports available at '''[[Resource Centres OLA and Resource infrastructure Provider OLA reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']]
 
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"
|-
| '''Service Level: '''
'''ROD Performance Index''' ticket/[https://documents.egi.eu/document/1089 Report]
 
| '''Jan'''
| '''Feb'''
| '''Mar'''
| '''Apr'''
| '''May'''
| '''Jun'''
| '''Jul'''
| '''Aug'''
| '''Sep'''
| '''Oct'''
| '''Nov'''
| '''Dec'''
|-
| '''2011'''
| -
| -
| -
| -
| -
| -
| -
| -
| -
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2011-10.pdf 10/11]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2011-11.pdf 11/11]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2011-12.pdf 12/11]
 
|-
| '''2012'''
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-01.pdf 01/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-02.pdf 02/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-03.pdf 03/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-04.pdf 04/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-05.pdf 05/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-06.pdf 06/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-07.pdf 07/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-08.pdf 08/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-09.pdf 09/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-10.pdf 10/12]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-11.pdf 11/12]
 
| &nbsp; <br>
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2012-12.pdf 12/12 ]
 
|-
| '''2013'''
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-01.pdf 01/13]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-02.pdf 02/13]
 
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-03.pdf 03/13]


= Future plans<br>  =
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-04.pdf 04/13]


In the future the metric will also include no. alarms closed in NON-OK status without explanation. This will need some implementation effort.  
|
[https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-05.pdf 05/13]


'''Issues to be implemented'''<span style="font-weight: bold;">:</span>  
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-06.pdf 06/13]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-07.pdf 07/13]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-08.pdf 08/13]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-09.pdf 09/13]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-10.pdf 10/13]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-11.pdf 11/13]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2013-12.pdf 12/13]
|-
| '''2014'''  
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2014-01.pdf 01/14]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=OlaMetrics_2014-02.pdf 02/14]
| ----<br>
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=2014-04%20ROD%20performance%20index%20report.pdf 04/14]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=2014-05%20ROD%20performance%20index%20report.pdf 05/14]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=2014-06%20ROD%20performance%20index%20report.pdf 06/14]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=1&filename=2014-07%20ROD%20performance%20index%20report.pdf 07/14]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=2&filename=2014-08%20ROD%20performance%20index%20report.pdf 08/14]
| [https://documents.egi.eu/secure/RetrieveFile?docid=1089&version=2&filename=2014-09%20ROD%20performance%20index%20report.pdf 09/14]
| <br>  
| <br>  
|
|}


*Taking into account holidays periods in alarms ageing
[[Category:Service_Level_Management]]
*Automatic check if site/node is in downtime while alarm is closing
[[Category:Deprecated]]
*Automatic check if node is not in production while alarm is closing
*In case of SCHEDULED interventions, the monthly metrics calculation should automatically take the scheduled downtime into account. At the time the metrics are computed, the application which does such calculation should access the GOC PI to determine which regional nagios machines were in downtime, and include that restriction in the calculation.

Latest revision as of 09:29, 10 August 2018

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security



Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.

The ROD performance index (formerly known as ROD OLA metric) was introcuded to track the level of Grid Oversight service delivered by Operations Centres according to Resource Provider OLA.

The index was accepted during Technical Forum 2011 in Lyon and is available on EGI Operations Portal. (choose Metrics tab).

Definition

ROD performance index is the sum of:

  • No. of ticket expired* in the operations dashboard daily
  • No. alarms older than 72h appearingin operations dashboard daily

A ticket in counted as expired in the Operations Portal dashboard if the "Expiration date" is set at a time in the past. The "Expiration date" field is set according to | escalation procedure, but can be freely changed by ROD. It refers to the date when the status of issue should be checked next time.

The ROD performance index is calculated monthly from the data gathered by EGI Operations Portal. It does not take into account weekends.

Threshold

The maximum value of the index must be 10. Above this value ROD teams has to provide explanation and provide a plan of improvement of the oversight service.


Recalculation procedure in case of intervention on the NGI SAM or the operations dashboard

Prerequisite:

  1. In case of problems with the regional SAM, Resource infrastructure Provider should create a GGUS ticket to SAM team.
  2. In case of work carried out on regional SAM the Resource infrastructure Provider should declare downtime in GOC DB.

Procedure steps:

  1. When an Operations Centre get a ticket from EGI Operations about ROD performance, the Operations Centre should provide GGUS ticket or a link to SAM or the operations dashboard downtime page in GOC DB.
    • If ROD performance index is below 10 items, NGI can create a GGUS ticket to EGI Operations asking for recalculation
  2. Based on GGUS trouble tickets referenced in prerequisites, or on the GGUS ticket opened by the Operations Centre to MyEGI requesting for A/R recalculation, or GOC DB service downtime entry, EGI Operations, knowing when the problem occurred,
    can remove the metrics items for given days from final report pdf.

Performance reports

Since October 2014 reports available at Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page

Service Level:

ROD Performance Index ticket/Report

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2011 - - - - - - - - -

10/11

11/11

12/11

2012

01/12

02/12

03/12

04/12

05/12

06/12

07/12

08/12

09/12

10/12

11/12

 

12/12

2013

01/13

02/13

03/13

04/13

05/13

06/13 07/13 08/13 09/13 10/13 11/13 12/13
2014 01/14 02/14 ----
04/14 05/14 06/14 07/14 08/14 09/14