Closed andreh12 closed 7 years ago
We have the test case of unidentified-problem which was caught on development instance:
http://daq-expert-dev.cms/nm/archive?source%5B%5D=UnidentifiedFailure&page=1
I suggest we change the suggested messages from
Reason for no trigger rate could not be identified
- make an elog entry
to
Trigger rate is zero. The problem could not be identified.
- recover the system according to instructions from shifter bulletin board
- make an elog entry
discussing with @gladky we propose the introduction of a logic module which fires when
This will allow to find such cases in the notification manager archive more easily and help to improve the software to identify not yet caught cases in the future.
More specifically, this new logic module will check whether
NoRateWhenExpected
has fired but no logic module inheriting fromKnownFailure
has identified a problem.