Physics data on tape at CERN
Click for larger picture
CTA Monitoring
Client-side Monitoring
Experiment client-side dashboards allow CTA operations to understand how our users perceive CTA infrastructure performance.
ATLAS Monitoring
The ATLAS DDM team has developed a comprehensive dashboard that tracks various metrics for all the Rucio back-ends in real time. This dashboard is very complete but requires many parameters to monitor a single endpoint. Note that times are in UTC.
ALICE Monitoring
The ALICE Storage Endpoints (SE) are:- SE Name: CERN-CTA. AliEn Name: ALICE::CERN::CTA. Instance for write tests. On the CTA side this is ctaalicepps
- SE Name: CERN-CTARO. AliEn Name: ALICE::CERN::CTARO. Read-only instance for recall tests, SSD+spinning disks. On the CTA side this is ctaalicero
Transfer Middleware Monitoring (FTS)
ATLAS, CMS, LHCb and several of the non-LHC experiments use the File Transfer Service (FTS), CERN's intermediate file transfer middleware, to transfer files to and from CTA. Rucio and Dirac do not make XRootD calls directly, instead delegating all CTA transfers to FTS. This allows each file transfer to be tracked and traced to quickly diagnose the cause of any errors.
ATLAS FTS Monitoring
CMS FTS Monitoring
Disk Buffer Monitoring
Each CTA instance has its own dedicated EOS disk buffer, which is monitored using its EOS Control Tower.
Production Instances
Pre-Production Instances (PPS)
Tape Backend Monitoring
This low-level monitoring can only be viewed by tape operations and developers (orgId=29). It provides performance metrics of CTA software, tape session history and real-time tape drive I/O speed.