Difference between revisions of "Service Level Target - ROD performance index"
m (moved Grid operations oversight/ROD performance index to ROD performance index: Wiki space review (RT 4614))
Revision as of 17:02, 6 December 2012
|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|EGI Infrastructure Operations Oversight menu:||Home •||EGI.eu Operations Team •||Regional Operators (ROD)|
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.
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.
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 here
Recalculation procedure in case of intervention on the NGI SAM or the operations dashboard
- 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 work carried out on regional SAM or operations dashboard the Resource infrastructure Provider should declare downtime in GOC DB.
- 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.
- If ROD performance index is below 10 items, NGI can create a GGUS ticket to COD 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,
can remove the metrics items for given days from final report pdf.
In the future the metric will also include no. alarms closed in NON-OK status without explanation. This will need some implementation 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.