If Subaru adds an ability to match STS text data using RE or wildcard, PFS could specify for each data sources that it is offline by setting its text data to "OFFLINE" or some other standard string. Will this work?

I think we had agreed to have some monitoring mechanism whether each actor is connected and live to the MHS server, and also to expose these status as "status" from (a) monitoring actor, no?
If it is possible to map and push these as STS status (or just flag/binary one), it seems request is implemented.

Yoshida, Hiroshige For MCS I was thinking of a larger switch. Not per-datum, but applying to "PFS MCS" or "PFS PFI". The "offline"/"online" switch on the GUI: is there a way to control that?

But yes, regexp matching would also be nice, so that we could express things like: isAlarm = not (OK or OFFLINE). Clearly per-instrument switches will not work for everything, so we will need per-datum control.

shimono We need to distinguish between an actor/device being offline on purpose, or disconnected because of a failure. We will need alertsActor commands to declare known disconnections, and those will need to be passed on to STS so that all the sources do not alarm. I just did not see a good mechanism for doing so.

A set of metrics in the same group (e.g., "Instrument: PFS MCS") can be enabled / disabled at once (there are online / offline links at the top of the table).

Yes. But can that be done without the GUI?

No.

Yoshida, Hiroshige Is that "No" saying that the functionality cannot be added?

No. We (= Subaru) could implement such a functionality, e.g., as a microservice. We have to figure out how to AA (same for STSradio), however.