Skip to content

Cell : increase detail in monitoring message published (for use by L1 page)

Tom Williams requested to merge feature/cell-increase-detail-in-monitoring-message into master

This merge request addresses issue #2 (closed) , by updating the implementation of the CellContext and SystemAnalyzer classes to improve the monitoring status message that is published by the SWATCH cell (and consumed by the L1 page).

This message will now contain the relative ID paths to the monitorable object / metric descendants of processors & DAQ-TTC managers that are found by crawling down the monitoring tree from each child of each processor / DAQ-TTC manager, and stopping when multiple child metrics / monitorable objects at the next level down give rise to the system's monitoring state.

E.g. For a system whose processors have the following sub-structure ...

algo
  rateTypeA
    metric1
    metric2
  rateTypeB
    metric1
    metric2
ttc
  metric1
  metric2
readout
  metric1
  metric2

If the system's error/warning/unknown monitoring status is caused by algo.rateTypeA.metric1 and ttc.metric1, the message will be: Error components : algo.rateTypeA.metric1, ttc.metric1

If the system's monitoring status is caused by algo.rateTypeA.metric1, algo.rateTypeA.metric2 and ttc.metric1, the message will be: Error components : algo.rateTypeA, ttc.metric1

If the system's monitoring status is caused by algo.rateTypeA.metric1, algo.rateTypeB.metric2 and ttc.metric1, the message will be: Error components : algo, ttc.metric1

Merge request reports