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
Line 25: Line 25:
<br>
<br>


== Recalculation procedure in case of intervention on the regional NAGIOS or dashboard<br> ==
== Recalculation procedure in case of intervention on the regional NAGIOS or dashboard<br> ==


'''Prerequisite''':
'''Prerequisite''':  


#In case of problems with synchronization between regional dashboard NGI should create a GGUS ticket to Operations Portal team.  
#In case of problems with synchronization between regional dashboard NGI should create a GGUS ticket to Operations Portal team.  
#In case of problems with the regional Nagios, NGI should create a GGUS ticket to SAM team.
#In case of problems with the regional Nagios, NGI should create a GGUS ticket to SAM team.  
#In case of work carried out on regional Nagios or dashboard NGI&nbsp;should declare downtime in GOC DB.
#In case of work carried out on regional Nagios or dashboard NGI&nbsp;should declare downtime in GOC DB.


<br>


'''Procedure steps:'''


'''Procedure steps:'''
#When NGI get a ticket from COD about ROD performance NGI should provide GGUS ticket or link to Nagios or dashboard downtime page in GOC DB.  
 
#Based on GGUS trouble tickets referenced in prerequ, or on the GGUS ticket opened by NGI 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.
#When NGI get a ticket from COD about ROD performance NGI should provide GGUS ticket or link to Nagios or dashboard downtime page in GOC DB.
#Based on GGUS trouble tickets referenced on 1./, or on the GGUS ticket opened by NGI to GridView 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.
 
 


== Future plans<br>  ==
== Future plans<br>  ==

Revision as of 11:10, 27 December 2011

ROD OLA metric

ROD OLA metric was introcuded to track the level of Grid Oversight service delivered according to Resource Provider OLA.

The metric was accepted during Technical Forum 2011 in Lyon and is available on EGI Operations Portal.


How the metrics is calculated?

The metric is calculated monthly from the data gahtered by EGI Operations Portal. It does not take into account weekends.


ROD OLA metric sum of:

  • No. of ticket expired appearance
  • No. alarms older than 72h appearance

The threshold was set to 10 items. Above this value ROD teams has to provide explanation and improvement plan.\


Recalculation procedure in case of intervention on the regional NAGIOS or dashboard

Prerequisite:

  1. In case of problems with synchronization between regional dashboard NGI should create a GGUS ticket to Operations Portal team.
  2. In case of problems with the regional Nagios, NGI should create a GGUS ticket to SAM team.
  3. In case of work carried out on regional Nagios or dashboard NGI should declare downtime in GOC DB.


Procedure steps:

  1. When NGI get a ticket from COD about ROD performance NGI should provide GGUS ticket or link to Nagios or dashboard downtime page in GOC DB.
  2. Based on GGUS trouble tickets referenced in prerequ, or on the GGUS ticket opened by NGI to MyEGI requesting for A/R recualculation, or GOC DB service downtime entry, COD, knowing when the problem occurred,
    can remove the metrics items for given days from final report pdf.

Future plans

In the future the metric will also include no. alarms closed in NON-OK status without explanation. This will need some inplementation effort.

Issues to be implemented:

  • Taking into account holidays periods in alarms ageing
  • Automatic check if site/node is in downtime while alarm is closing
  • 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.