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. Chris Ford also points out that multiple users using tstopr accounts (e.g. in lab3/neh) can conflict (like last settings of GUIs perhaps?). This could conceivably be resolved by the resource manager that is in-progress. Ric points out that most experts run as themselves (e.g. claus, caf, ...) and the
active-detector file andlog files go into their home directory (even if they use tstopr via procmgr.conf) so there is no conflict there.
...
- reusing the operator account "tstopr" is also a problem
- $HOME directory holds
log files,active detectors file, etc. - regarding "site," does the benefit of enabling "tst" (or any other instrument name) to be reused justify the added complexity?
- A simple solution is to require unique instrument names.
some thoughts from ric
'Instrument' ("hutch") is used to access configDb and create the file path for recording
So, don't want to prepend 'site' too early
Maybe want to use it only with grafana or are there other places that would benefit?
There is no proposed regulation on the 'site' value, so some people will ignore it, some will use their initials and some will do the intended thing
.cnfs would need to be changed in order to set it, which may be forgotten
Maybe change 'site' to 'instrument_prefix' (better name needed)?
There is a worry that 'site' provides the illusion that a given partition is unique in a given site when this is not necessarily so
For example, the case when two different site names are given to the same physical site
- Maybe better to leave things as they are and deal with the very occasional occurrence of ambiguity in grafana by clicking on the item, selecting View and hovering on the value. This will show the source instance: