Page History

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", a.k.a. primary readout-group)
- determines procmgr ports on the shared drp from primary readout group (must be different for rix/tmo to share drp)
- also maps to accounts that procmgr uses like tmoopr, uedopr, etc. using /etc/procmgrd.conf
- also used by database to map to experiment-name for each "station" (https://pswww.slac.stanford.edu/lgbk/lgbk/ops#switch)
instrument: ued, tmo, rix
site (proposed, string): subnet (or location?) and the root xpm that procmgr uses?

...

the issue only realistically occurs for tst for grafana (in other case, instrument names like tmo,rix,ued are the "site" (i.e. the subnet and root-xpm))
doesn't feel right for expert-only tst case to impact general design for users
feels like "hutch" gets used by default for grafana, but perhaps could be overridden by experts with optional kwarg overriding usage of hutch=tst to something more unique, e.g. tstued?

Page tree