Log package

This section provides a quick overview of the log packages of the IBM Storage Fusion.

The following log packages are available in the Logs page:
  1. Global Data Platform
  2. Data Foundation
  3. Backup and restore
  4. Data Cataloging

Every log package contains a HealthManagerCR folder expect for the Backup & Restore service.

Global Data Platform

Logs related to storage availability. The Global Data Platform log package mainly contains the folders for the following namespaces:
Important: By default, it collects the logs from the IBM Storage Fusion namespace and the namespace where the service is deployed.
  • storage fusion namespace
  • ibm-spectrum-scale-namespace
  • ibm-spectrum-scale-csi-namespace
  • ibm-spectrum-scale-operator-namespace

Global Data Platform log packages contain both the custom and cluster resources. The custom resources such as spectrumfusions, scalemanagers, scaleclusters, and nodes. The cluster resources such as storageclasses.

Follow the steps to collect Velero namespace logs:
  1. On the Global Data Platform service, manually add the Velero namespace under the namespaces in the serviceability section of the FusionServiceDefinition instance.
  2. It ensures that the Velero namespace logs are collected as part of log collection for the Global Data Platform service.
  3. The Velero namespace is specified in ramen-dr-cluster-operator-config configmap in the ibm-spectrum-fusion-ns namespace.

It also includes the scale must-gather folder with the relevant log files.

Data Foundation

Logs related to storage availability. The Red Hat® OpenShift® Data Foundation log package mainly contains the folders for the following namespaces:
Important: By default, it collects the logs from the IBM Storage Fusion namespace and the namespace where the service is deployed.
It includes the Openshift-storage and Openshift-local-storage folder with the relevant log files.
Note: Data Foundation log status shows partial if any of the namespaces are not available, but you can upload and download partial logs.

Red Hat OpenShift Data Foundation log packages contains both the custom and cluster resources. The custom resources such as spectrumfusions, odfmanagers, odfclusters, fusionservicedefinitions, fusionserviceinstances, storageclusters, cephclusters, localvolumediscoveries, localvolumediscoveryresults, localvolumesets, catalogsources, volumesnapshotclasses, and clustercsidrivers.

The cluster resources such as persistentvolumes, clusterrolebindings, storageclasses, and storageclassclaims.

Follow the steps to collect Velero namespace logs:
  1. On the Data Foundation service, manually add the Velero namespace under the namespaces in the serviceability section of the FusionServiceDefinition instance.
  2. It ensures that the Velero namespace logs are collected as part of log collection for the Data Foundation service.
  3. The Velero namespace is specified in ramen-dr-cluster-operator-config configmap in the ibm-spectrum-fusion-ns namespace.

Backup and restore

Logs related to backup and restore of your workload applications. The backup and restore log package mainly contains the folders for the following namespace.
Important: By default, it collects the logs from the IBM Storage Fusion namespace and the namespace where the service is deployed.
ibm-backup-restore
It contains the logs and object definition files for all of the major resources under this namespace. For example, routes, pods logs, deployments, deamon sets, persistent volumes, and config maps.
Note: It includes the Kubernetes events that are associated with the resource. If any resource does not exist, then it can be skipped.

Data Cataloging

Logs related to Data Cataloging service. The Data cataloging log package mainly contains the folders for the following namespace.
Important: By default, it collects the logs from the IBM Storage Fusion namespace and the namespace where the service is deployed.
ibm-data-cataloging
It contains the logs and object definition files for all of the major resources under this namespace. For example, routes, pods logs, deployments, deamon sets, persistent volumes, and config maps.
Note: It includes the Kubernetes events that are associated with the resource. If any resource does not exist, then it can be skipped.