Executive summary (Aug. 4, 2022): Ric has highlighted an issue where grafana simultaneously sees the "tst" instrument running in both lab3 and neh (for example). This can be seen in this picture where there are two columns for "Time" "NumL0" and "Dead" in the white box. Currently grafana uses "instrument" and "partition" to identify which data to display. Ric proposes introducing a new concept: a "site" string.
fundamental concepts:
- partition (formerly known as "platform"): determines procmgr ports on the shared drp from primary readout group
- instrument: ued, tmo, rix (also maps to accounts that procmgr uses like tmoopr, uedopr, etc.)
- site (proposed, string): subnet (or location?) and the root xpm that procmgr uses?
problem:
(1) grafana tst in lab3 conflicts with tst in neh (user will see results from both)
(2) tst in rix conflicts with tst in tmo (i.e. within one subnet)
currently two grafana "labels": instrument(e.g. tst), partition (primary readout group)
can run tst in lab3 or in neh.
options:
(1) we say "tst" can only run in one (subnet-plus-root-xpm)
(2) invent a new field for grafana: "site" (defined above)
(3) instrument field could include a new sub-string, like "site:instrument"
could we make root-xpm number unique across the lab? no, because there can only be 0-6.
if we create "site":
- put it in the .cnf file or setup_env? (manually assigned). ric proposes strings:
e.g. lab3, ued, asc, neh2 (location+rootxpm), neh3 (location+rootxpm), txi
- when code creates grafana metrics, has to add "site" (drp, teb, meb, ami)
- have an extra drop-down menu on the grafana pages to select site
- site could be used by murali as well in databases
fundamental tuple:
site:instrument:partition(aka primary readout group)
Overview
Content Tools