Transfer some DQSegDB monitors from old Dashboard to Dashboard2
There are several monitors on the old Dashboard system (called Dashboard1 in this ticket) that should be transferred to the new Dashboard2 system.
The existing monitors on both systems are tracked here: https://wiki.ligo.org/Computing/DQSegDBMonitorsAndScripts#Monitoring_overview
Dashboard1 monitors that should definitely be transferred or reproduced with new code on Dashboard2:
- segments-web:
ping4
,https
, andcert
native monitors on Dashboard2 -
Compare dqxml on segments-cit to IFO for {GEO,LHO,LLO,Virgo}
on Dashboard1 -
{G1,H1,L1,V1} segments in DB match segs. in DQ XML files
on Dashboard1 -
Status of DB running on segments{,-backup}
on Dashboard1 -
Status of services running on segments{,-backup,-web,-dev}
on Dashboard1
Dashboard1 monitors that maybe should be transferred or reproduced with new code on Dashboard2:
-
{G1,H1,L1,V1} publisher finds correct DQ XML files
on Dashboard1 (need to review what exactly this monitor does and see if it's still needed) -
Space usage on /backup/segdb/ and /ifocache/
- is this already monitored somewhere on Dashboard2? if so, just add that to the dqsegdb monitor page or a variation of it; if not, decide whether to use this monitor or get new monitors added -
{DMT-ANALYSIS_READY,GRD-ISC_LOCK_OK} Segment Validation {LHO,LLO}
- are these 4 monitors completely replaced by more specific monitors?
Dashboard1 monitors that should definitely not be transferred to Dashboard2:
-
Pending DQXML Files {LHO,LLO}
- the monitor's task is now covered by 2 other monitors (dqxml-latency-{h1,l1} verifies that new DQXML files have been delivered to the machine and "{H1,L1} publisher finds correct DQ XML files" verifies that the publisher finds the unpublished DQXML files that are on the machine; it was decided to turn this monitor off on Dashboard1 and not transfer it to Dashboard2 (see notes here and here)
Dashboard1 monitors that have already been transferred or reproduced with new code on Dashboard2:
-
segments{,-backup,-dev}.ligo.org Ping
- these monitors are reproduced byping4
andhttps
native monitors on Dashboard2 -
G1 HOFT Segment Latency
,{H1,L1} {GRD,HOFT} Segment Latency
, andV1 DQ META STATUS ITF Segment Latency
- these monitors are reproduced bydqsegdb-latency-g1hoft
,dqsegdb-latency-{h1,l1}{dq,hoft}
, anddqsegdb-latency-v1hoft
monitors with new code on Dashboard2
Edited by Robert Bruntz