Pole 3 – Dashboard Assessment COD 20 - Helsinki 1

Update of the new features or improvements since last COD meeting Contents of next release Medium term plan : Regionalization Feedback needed from the federations

Update since last COD meeting https://cic.gridops.org/index.php?section=roc&page=dashboard&subpage=metrics 1) ROD metrics : - Metric 0, 1 , 2 , 3: * New Alarms younger than 24 h, 48 h , 72 h and > 72 h (working day) * Evaluated once in the day - Metric 4 , 5 : * New Alarms closed in the day * Metrics evaluated on every changes - Metric 6 ,7, 8 : * Metrics giving the status of the tickets from GGUS resources - Metric 9,10 : * Metrics giving info related to the action on the Tickets in the day (info directly taken from the dashboard) 3 3

Update since last COD meeting 2) The indication of why the site is in the ccod dashboard => Indication presented when the mouse is passed over the name of the site . 3) propose an option into preferences page to hide alarms <24 h, and add an indication about it => Done in the Alarms page . 4) Don't display downtimes AT RISK (or maybe a different color) 5) C-COD in copy with handover log 6) options to hide sites without alarms and problems => Added in the Preferences Page

Update since last COD meeting 7)Notepad improvements Present in Alarm View and dashboard Add the opportunity to cut the history where you want Possibility to put entries for more then one people in the same time 10) Bug : correct the link into ticket into the regional dashboard for the alarm 11) An info is disayed when there is no alarms and no tickets into the dashboard 12) display a different icon on the dashboard for masked alarms 13) Bug: display pre defined CN in the submitter field 14) Study the utility of the comparator tool => this option has been removed – A discussion will take place with GSTAT team on this topic (it seems that they are working on such a tool)

Next release : August 1) alarm age should not increase on weekends => Done 2) C-COD Metrics 3) Declare to a site that is “automatically” transferred to C-COD 4) Case of a downtime longer than 1 month => site present in C-COD Dashboard 5) display CORE services at the beginning of the page for central services 6) More explicit error message coming from the web service 7) ticket status is changed to 2nd mail before 2nd mail was send 8) Add the opportunity to open tickets against Operational tools 9) Need of an interface with the local helpdesk (need to be defined) 10) Add checkboxes to hide what you want in the dashboard 11) decrease the slowness of dashboard This work is on going and is related to the re-organization of information . The computation must be done in Lavoisier and not in the php layer . 12) Integrate GOC DB info using the Programmatic Interface

Regionalization The work is divided around 2 themes : - the extraction of the code outside the portal : it means solving problem of dependencies , of absolute urls , of absolute reference , of absolute variables . The delivered package will work on one machine with the Web Service Lavoisier , some php files and a Mysql DB . - regionalize the resources and their organization : we have to split the resources for 2 reasons : to be sure that resources concerning one ROC is not accessible by other ROCs , and to increase the efficiency of the dashboard . This re-organization will take place around our Web Service Lavoisier that will take on the specificities of the resources of each region . We will continue to propose a Central View for the regions that don't want their own instance . A prototype will be normally proposed at EGEE 09 conference .

What we need to know now - What remains from the COD section ? => Do you think that is you useful to keep this section ? How can we transform it if necessary ? - What other features in the Portal are useful for you ? - Do you will continue to use the dashboard after EGEE III ?