Implement minimal "fault management" capability

[akhenry]

Is your feature request related to a problem? Please describe.
A basic "fault management" capability that summarizes the current state of alarms across all subsystems.

Describe the solution you'd like
Add a dedicated alarm summary screen to Open MCT.

Describe alternatives you've considered
If exposed as telemetry points, alarms can be listed in telemetry tables. This solution shows both current and historical alarms, which generates a lot of visual noise.

[rukmini-bose]

TESTING INSTRUCTIONS

1. Select Fault Management object from the Object Tree.
2. Ensure that every fault contains a criticality icon.
3. Make sure selection of one fault does the following: (a) Selected fault is highlighted blue to indicate it being selected. (b) Inspector will display the appropriate fault details for that fault.
4. Make sure that selecting multiple faults eliminates the fault details from inspector.
5. Ensure that the disposition button for an individual fault works by selecting acknowledge or shelve. Then, navigate to each view and ensure that the correct faults appear in the correct disposition views. Also, check the same with selecting multiple faults and using the larger disposition options located directly under search.
6. Ensure that search works properly by entering keywords and observing the correct faults are shown.
7. Check to see if the sort button works and changes according to the options selected (Newest First, Oldest First, Severity)
8. When selecting the Acknowledged view, ensure that the criticality icons are not blinking. and that the criticality icon includes a checkmark.
9. When selecting the Unacknowledged view, check that the criticality icons are blinking.
10. When selecting the Shelved view, check that the contents of the fault are italicized and _slightly greyed out, and criticality icon is not blinking.
11. When selecting Standard View, ensure that only acknowledged and unacknowledged faults appear, and its criticality icons are blinking accordingly.
12. Shelve a fault for a short period of time. When the time specified runs out, ensure that the fault returns back to its Unacknowledged state and is NOT shelved.

Main view with selected fault

Disposition dialog

Acknowledged fault

Width < 600px in a layout

[jvigliotta]

Can't currently Acknowledge or Shelve a fault.

[jvigliotta]

Seeing this error when "Shelving" a Fault. (not my fault)

[rukmini-bose]

(1) Cannot currently acknowledge/ shelve faults without getting the error message that Jamie gets.

(2) When opening up the details in the inspector, the "Live Value" is not updating in the similar fashion as it is in the main dashboard. It is only capturing the values that were taken at the time of selecting the fault.

[unlikelyzero]

Still waiting for @unlikelyzero to close out once we get yamcs role permissions

[charlesh88]

Testathon 07-08-22: verified NOT FIXED

• Shelved alarms still appear in the Unacknowledged list view and display the blinking cursor, but shouldn't do either.

- Only one fault available, can't verify sorting.

[jvigliotta]

If we don't have the role to manage faults, should we hide fault management or possibly show a notification when someone unsuccessfully tries to ack or shelve?

[davetsay]

partially verified the below. unable to verify other steps due to lack of role

• Select Fault Management object from the Object Tree.
• Ensure that every fault contains a criticality icon.
• Make sure selection of one fault does the following: (a) Selected fault is highlighted blue to indicate it being selected. (b) Inspector will display the appropriate fault details for that fault.
• Make sure that selecting multiple faults eliminates the fault details from inspector.
• Ensure that search works properly by entering keywords and observing the correct faults are shown.
• When selecting the Unacknowledged view, check that the criticality icons are blinking.

[akhenry]

To enable shelving and acknowledging of alarms:

1. Create an ssh tunnel to the test environment. ie.
   ssh -L 8090:localhost:8090 <yamcs hostname>
2. Click on the admin menu at the top of the screen
3. Navigate to Access Control > Users
4. Click on your user
5. Apply the Ground Control (gc) role.
6. Save Changes
7. Refresh Open MCT and you should be able to acknowledge and shelve faults.

[akhenry]

@charlesh88 The issue here is that "shelved" and "acknowledged" are orthogonal states in the data design. The data design allows a fault to be either shelved and acknowledged, or shelved and unacknowledged. A shelved alarm does not get acknowledged when it is shelved. I have tweaked our UI so that it matches the behavior in Yamcs, but be aware that this is now incorrectly reflecting the state of the alarms.

I think this is ok because I think it matches user expectations, even if the pedantic logician in me is grumbling about it.

[akhenry]

Testing instructions

1. From the "standard" view, shelve an alarm
2. Confirm that the shelved alarm now only appears in the "shelved" view, and does not appear in the the "Acknowledged" or "Unacknowledged" views.
3. Unshelve the alarm and confirm that it returns to the "Standard View", and the "Unacknowledged" view.
4. Acknowledge the alarm
5. Confirm that it appears in the "Acknowledged" View, and not the "Unacknowledged" or "Shelved" views.

[charlesh88]

Testathon 07-11-22 verified fixed. Filed #5481 for console errors being thrown.

[davetsay]

Verified (except could not test filters/sort on multiple alarms)