NL Cloud Monitor Instructions

Introduction

This page will give a step-by-step instruction for the shifters (of the ATLAS NL-cloud regional operation) to check through several key monitoring pages used by Atlas Distributed Computing (ADC). Those key monitoring pages were also monitored by official ADC shifters (e.g. ADCoS, DAST).

The general architecture of ADC operation is shown below. The shifters that we are concerning here is part of the "regional operation team". The contribution will be credited by OTSMU.

General architecture of the ADC operation

Things to monitor

Follow the instructions below for checking different monitoring pages and notify the NL cloud squad team accordingly via adc-nl-cloud-support@nikhef.nl.

ADCoS eLog

ADCoS eLog is mainly used by ADC experts and ADCoS shifters to log the actions taken on a site concerning a site issues. For example, removing/adding site from/into the ATLAS production system. The shifter has to notify the squad team if there are issues not being followed up for a long while (~24 hours).

The eLog entries related to NL-cloud can be found here.

DDM Dashboard

DDM Dashboard is used for monitoring the data transfer activities between sites.

The main monitoring page is explained below

DDM Dashboard Explaination

There are few things to note on this page:

1. the summary indicates the data transfer "TO" a particular cloud or site. For example, transfers from RAL to SARA is categorized to "SARA"; while transfers from SARA to RAL is catagorized to "RAL".
2. the cloud is label with its Tier-1 name, for example, "SARA" represents the whole transfers "TO" NL cloud.
3. it will be handy to remember that "yellow" bar indicates transfers to NL cloud.

To check this page, here are few simple steps to follow:

1. look at the bottom-right plot (total transfer errors). If the yellow bar persists every hour with a significant number of errors. Go to check the summary table below.
2. To check the failed transfers to NL cloud, click on the "SARA" entry on the summary table. The table will be extended to show the detail transfers to the sites within NL cloud. From there you can see which site is in trouble.
3. When you identify the destination site of the problematic transfers, you can click on the "+" sign in front of the site, the table will be extended again to show the "source site" of the transfers. By clicking on the number of the transfer errors showing on the table (the 4th column from the end), the error message will be presented. A graphic instruction of those steps is shown below.

DDM Dashboard Explaination

Report the problem to the NL squad team when the number of the error is high.

There are some cases that you don't need to report:

1. Don't report the problem if the error message indicates that it's a "SOURCE" error (you can see it on the error message).
2. Don't report the problem if the site is in downtime. The downtime schedule can be found here: http://lxvm0350.cern.ch:12409/agis/calendar/
3. Don't report the problem again if the same error remains during your shift and you have reported earlier.

GangaRobot

GangaRobot is a site functional test for running analysis jobs. Sites fail to pass one of the regular tests in past 12 hours will be blacklisted. The user analysis jobs submitted through the gLite Workload Management System (WMS) from Ganga will be instrumented to avoid being assigned to those problematic sites.

The currently blacklisted site can be found here.

The shifter has to notify the NL squad team when any one of the sites in NL cloud shows up in the list.

Quick links

• Contact NL squad team
• ADC eLog (NL related entries)
• DDM Dashboard (last 4 hours overview)
• Panda production jobs monitoring
• Panda analysis jobs monitoring
• Panda queues for NL-cloud sites
• GangaRobot site blacklist