Appreciate the discussion. My understanding follows. I don't know if it says this anywhere in so many words, but it looks to me like there are 3 states:
- Gray - - Indicator not enabled
- Green - - Indicator enabled and monitoring for condition
- Red (flashing) - - Indicator "tripped"
On the Alarm Settings page, this is the header for options: These are pretty clear to me starting from the left through "Set sound file". It seems here we've been exploring Latches and Latch hrs. This is sort of orthogonal in the sense that it affects the indicator behavior after the condition is met ... or cleared??
The effect of "Notify" isn't clear to me. Anyone?
When I noticed a message in the Service Console Log a while back that said a new build was out, I decided that this was something I wanted easy access to from the Admin dashboard. So even before the indicator I added this to my "Local" dropdown... I just put a sym-link in interface/ to that file and access it as plain text for the moment.
As others have mentioned, I've been running (a much older version of) CMX as a service for quite some time under systemctl. As a result I got accustomed to using journalctl for logging, which I sort of like as it spans restarts, and I use it for other support services I've developed. (Just recalled that I had been running it under nohup - which the CMX -service flag more or less handles for running without a console.) At any rate, having the Service Console Log web-accessible has been helpful. Might be a useful addition.
As far as indicators, if it "new build" shows up in that log, should the indicator trip at the same time? And I would guess that latching doesn't add a lot of value for that particular indicator.