xrootd monitoring (xrootd native server)
1). Missing VO problem. According to Brian, VO should be properly resolved for all traffic with certificate authentication and VOMS usage. For CMS according to Stephan Lammel it is 98% of cases. Should be the same for ATLAS and LHCb (to be checked). ALICE does not use VOMS. Based on it we can assume that al traffic which we get with non-resolved VO is not for CMS, LHCb or ATLAS and therefore we do not care about it for our current usecase. Though we need to investigate case by case, whether it is true for servers which do not resolve VO properly
2). Very good result of comparison of the traffic as measured by new shoveler-collector with network traffic of the RAL xrootd servers demonstrated by Katy. THis is very encouraging.
3). CERN is progressing with the required restart of the EOS servers. Borja follows up with EOS team. Started with ALICE servers, which gives us an opportunity to validate throughput comparing with Monalisa.
4). Discussed why we have two different topics 'third party copy' and 'remote access' for US xrootd monitoring. If we understand correctly, 'third party copy' traffic is the one which is handled by FTS (FTS with xroot protocol). It is already properly monitored and could be that we do not need to consume it in the future. Related to it, we need to check whether we can differentiate traffic with different protocols for the transfers handled by FTS via WLCG dashboard. This functionality might be useful. Action: Julia will contact Diego to get more details.
5). Deployment of the new components at the US sites. Need to find out with Derek, what is the situation and what we might need to do in this respect. related to it, would be nice to be able to see data from the US new xrootd monitoring flow in the Dashboard in MONIT, asked Borja to enable it.
xrootd monitoring (dCache with xtootd door)
1). Julia got an answer from FNAl regarding dCache upgarde. Not planned before the end of January. This leaves very little time before DC24. Julia asked whether we can do integration work on the development infrastructure. No answer yet.
2). Traffic we get form Desy, not clear whteher it is a test server or production one. Whether Desy already upgraded to the new dCache release? If not when they plan to do so. Borja will clarify with Desy
3). Julia will follow up regarding Borja's request for CRIC API with CRIC team and come back with the answer asap.
getting data from ALICE for central monitoring tools
1). Julia asked Borja how xrootd monitoring data form ALICE is getting into MONIT. We would like to re-use the same mechanism for job monitoring. Need to have a discussion with Costin.
