The metric file_integrity_operator_node_failed is getting reset after restart of file-integrity-operator because of which existing alert NodeHasIntegrityFailure disappears.

File Integrity Operator 1.3.4

100%

1. Install File Integrity Operator and check "Enable Operator Recommended Monitoring" checkbox.
2. Create FileIntegrity custom resource and wait for the pods to initialize fine.
3. Simulate a failure condition and wait for NodeHasIntegrityFailure alert to stream.
4. Restart file-integrity-operator pod.
5. After couple of minutes the alert NodeHasIntegrityFailure will clear itself but the "oc get fileintegritynodestatuses" reports failure for the node on which failure condition was simulated.

The metric is getting reset after operator pod restart.

The operator should check the status of existing fileintegritynodestatuses and trigger NodeHasIntegrityFailure alert accordingly.