Chapter 3. Alerts

3.1. Setting up alerts

For internal Mode clusters, various alerts related to the storage metrics services, storage cluster, disk devices, cluster health, cluster capacity, and so on are displayed in the Block and File, and the object dashboards. These alerts are not available for external Mode.

Note

It might take a few minutes for alerts to be shown in the alert panel, because only firing alerts are visible in this panel.

You can also view alerts with additional details and customize the display of Alerts in the OpenShift Container Platform.

For more information, see Managing alerts.

3.2. Overprovision level policy control[Technology Preview]

Overprovision control is a mechanism that allows administrators to define a quota on the amount of PVCs consumed from a storage cluster, as per the specific application namespace. When you enable overprovision it prevents you from overprovisioning the PVCs. OpenShift provides a flexibility for defining constraints that limit the aggregated resource consumption at cluster scope with the help of OpenShift’s ClusterResourceQuota. With Overprovision control, ClusteResourceQuota is initiated and administrators can set the limit for consumed storage capacity per storage-class. The alarm then triggers at 80% of the capacity limit of the PVC.

Note

Overprovision level policy control is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information, refer to Technology Preview Features Support Scope.

For more information on deployment, refer to Product Documentation and select the deployment procedure according to the platform.

Perform the following steps to receive the Overprovision Control alerts:

  1. After deploying storagecluster (either from CLI or GUI)
  2. Label the application namespace.

    For example:

    apiVersion: v1
    kind: Namespace
    metadata:
      name: quota-rbd
      labels:
        storagequota: storagequota1
  3. Edit the storagecluster from the command line.

    For example:

    $ oc edit storagecluster -n openshift-storage ocs-storagecluster-name
  4. Add to StorageCluster.Spec an entry for Overprovision Control with the desired hard limit.

    For example:

    apiVersion: ocs.openshift.io/v1
    kind: StorageCluster
    spec:
      # ...
      overprovisionControl:
      - capacity: 27Ti
        storageClassName: ocs-storagecluster-ceph-rbd
        quotaName: quota1
        selector:
          labels:
            matchLabels:
              storagequota: storagequota1
  5. Save the modified storagecluster.
  6. Make sure that clusterresourcequota is defined.

    $ oc get clusterresourcequota -A
    $ oc describe clusterresourcequota -A