Clarifying FIO documentation

Author: sheriff-rh

modules/file-integrity-node-status-failure.adoc

@@ -2,6 +2,7 @@
 //
 // * security/file_integrity_operator/file-integrity-operator-understanding.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="file-integrity-node-status-failure_{context}"]
 = FileIntegrityNodeStatus CR failure status example
 
@@ -109,4 +110,14 @@ File: /hostroot/etc/resolv.conf
 Events:  <none>
 ----
 
-Due to the config map data size limit, AIDE logs over 1 MB are added to the failure config map as a base64-encoded gzip archive. In this case, you want to pipe the output of the above command to `base64 --decode | gunzip`. Compressed logs are indicated by the presence of a `file-integrity.openshift.io/compressed` annotation key in the config map.
+Due to the config map data size limit, AIDE logs over 1 MB are added to the failure config map as a base64-encoded gzip archive. Use the following command to extract the log:
+
+[source,terminal]
+----
+$ oc get cm <failure-cm-name> -o json | jq -r '.data.integritylog' | base64 -d | gunzip
+----
+
+[NOTE]
+====
+Compressed logs are indicated by the presence of a `file-integrity.openshift.io/compressed` annotation key in the config map.
+====