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"
| Line 1: | Line 1: | ||
= ROD OLA metric = | = ROD OLA metric = | ||
ROD OLA metric was introcuded to track the level of Grid Oversight service delivered according to [https://documents.egi.eu/secure/ShowDocument?docid=463 Resource Provider OLA]. | ROD OLA metric was introcuded to track the level of Grid Oversight service delivered according to [https://documents.egi.eu/secure/ShowDocument?docid=463 Resource Provider OLA]. | ||
The metric was accepted during Technical Forum 2011 in Lyon and is available on [https://operations-portal.in2p3.fr/dashboard/rodOlaMetrics EGI Operations Portal]. | The metric was accepted during Technical Forum 2011 in Lyon and is available on [https://operations-portal.in2p3.fr/dashboard/rodOlaMetrics EGI Operations Portal]. | ||
<br> | |||
== How the metrics is calculated? == | |||
== | The metric is calculated monthly from the data gahtered by EGI Operations Portal. It does not <span lang="en" id="result_box" class="short_text"><span class="hps">take</span> <span class="hps">into account</span> <span class="hps">weekends</span></span>. | ||
<br> | |||
'''ROD OLA metric sum of:''' | |||
*No. of ticket expired <span lang="en" id="result_box" class="short_text"><span class="hps">appearance</span></span> | |||
*No. alarms older than 72h <span lang="en" id="result_box" class="short_text"><span class="hps">appearance</span></span> | |||
<span lang="en" class="short_text"><span class="hps" /></span> | |||
'''The threshold was set to 10 items.''' Above this value ROD teams has to provide explanation and improvement plan.<br> | |||
== Future plans<br> == | |||
In the future the metric will also include no. alarms closed in NON-OK status without explanation. This will need some inplementation effort. <br> | |||
= | '''Issues to be implemented'''<span style="font-weight: bold;">:</span> | ||
*Taking into account holidays periods in alarms ageing | |||
*Automatic check if site/node is in downtime while alarm is closing | |||
*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 | *Automatic check if node is not in production while alarm is closing | ||
Revision as of 11:58, 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.
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