ATLAS Site Availability and Performance (ASAP)
Since December 2013, a new way for computing availability has been introduced. It's called ASAP / ATLAS Site Availability and Performance / ATLAS_AnalysisAvailability (depending where you look). From what I have gleaned about it, ASAP is a metric to replace ADCD site status; it’s not related the SAM tests. the status of "PandaResource" of an analysis queue is used by ASAP. A site is considered to be unavailable when its analysis queue is in test mode. This document will briefly describe some of the implications of this; it shall include
- How to get the important alerts
- Where to check ASAP site status online
- How to find ASAP related HC detailed status records
- How to use HC detailed status records to debug common scenarios (e.g. FAQ).
Contents
How to get the important alerts
Unfortunately, at the moment, when a queue is set to test mode, the notification email is sent to cloud support and doesn’t go to to our site admins. For some site admins, they may be able to subscribe to the list (atlas-support-cloud-uk@cern.ch) at [[1]]. Some admins without the necessary secutiry credentials can request to be subscribed; ask Elena Korolkova, Alessandra Forti or another GridPP representative of ATLAS.
Once you are getting the alerts, it's uisually pollible to set up message filters that can find the messages for your site by searching the subject field for the name of the queue. A list of all Panda queues can be found here: dashb-atlas-ssb.cern.ch.
Where to check ASAP site status
You can check the ASAP status here: wlcg-mon.cern.ch.
Blah Blah Blah
How to use HC detailed status records to debug common scenarios
Blah Blah Blah
