GlusterFS¶

The GlusterFS service on the {{ $labels.host }} host is down.

Raises when Telegraf cannot find running glusterd processes on the kvm hosts.

Not required

All GlusterFS services are down.

Raises when the Telegraf service cannot connect or gather metrics from the GlusterFS service, typically meaning the GlusterFS, Telegraf monitoring_remote_agent service, or network issues.

Not required

More than 80% of GlusterFS {{ $labels.volume }} volume inodes are used for 2 minutes.

Raises when GlusterFS uses more than 80% and less than 90% of available inodes. The volume label in the raised alert contains the affected GlusterFS volume.

Typically, you should not change the default value. If the alert is constantly firing, verify the available inodes on the GlusterFS nodes and adjust the threshold according to the number of available inodes. In the Prometheus Web UI, use the raise condition query for a longer period of time to define the best threshold.

For example, to change the threshold to the 90 - 95% interval:

1. On the cluster level of the Reclass model, create a common file for all alert customizations. Skip this step to use an existing defined file.

   1. Create a file for alert customizations:

      touch cluster/<cluster_name>/stacklight/custom/alerts.yml
      

   2. Define the new file in cluster/<cluster_name>/stacklight/server.yml:

      classes:
      - cluster.<cluster_name>.stacklight.custom.alerts
      ...
      

2. In the defined alert customizations file, modify the alert threshold by overriding the if parameter:

   parameters:
     prometheus:
       server:
         alert:
           GlusterfsInodesUsedMinor:
             if: >-
               glusterfs_inodes_percent_used >= 90 and \
               glusterfs_inodes_percent_used < 95
   

3. From the Salt Master node, apply the changes:

   salt 'I@prometheus:server' state.sls prometheus.server
   

4. Verify the updated alert definition in the Prometheus web UI.

{{ $value }}% of GlusterFS {{ $labels.volume }} volume inodes are used for 2 minutes.

Raises when GlusterFS uses more than 90% of available inodes. The volume label in the raised alert contains the affected GlusterFS volume.

Typically, you should not change the default value. If the alert is constantly firing, verify the available inodes on the GlusterFS nodes and adjust the threshold according to the number of available inodes. In the Prometheus Web UI, use the raise condition query for a longer period of time to define the best threshold.

For example, to change the threshold to 95%:

1. On the cluster level of the Reclass model, create a common file for all alert customizations. Skip this step to use an existing defined file.

   1. Create a file for alert customizations:

      touch cluster/<cluster_name>/stacklight/custom/alerts.yml
      

   2. Define the new file in cluster/<cluster_name>/stacklight/server.yml:

      classes:
      - cluster.<cluster_name>.stacklight.custom.alerts
      ...
      

2. In the defined alert customizations file, modify the alert threshold by overriding the if parameter:

   parameters:
     prometheus:
       server:
         alert:
           GlusterfsInodesUsedMajor:
             if: >-
               glusterfs_inodes_percent_used >= 95
   

3. From the Salt Master node, apply the changes:

   salt 'I@prometheus:server' state.sls prometheus.server
   

4. Verify the updated alert definition in the Prometheus web UI.

{{ $value }}% of GlusterFS {{ $labels.volume }} volume disk space is used for 2 minutes.

Raises when GlusterFS uses more than 80% and less than 90% of available space. The volume label in the raised alert contains the affected GlusterFS volume.

Typically, you should not change the default value. If the alert is constantly firing, verify the available space on the GlusterFS nodes and adjust the threshold accordingly. In the Prometheus Web UI, use the raise condition query for a longer period of time to define the best threshold.

For example, to change the threshold to the 90-95% interval:

1. On the cluster level of the Reclass model, create a common file for all alert customizations. Skip this step to use an existing defined file.

   1. Create a file for alert customizations:

      touch cluster/<cluster_name>/stacklight/custom/alerts.yml
      

   2. Define the new file in cluster/<cluster_name>/stacklight/server.yml:

      classes:
      - cluster.<cluster_name>.stacklight.custom.alerts
      ...
      

2. In the defined alert customizations file, modify the alert threshold by overriding the if parameter:

   parameters:
     prometheus:
       server:
         alert:
           GlusterfsSpaceUsedMinor:
             if: >-
               glusterfs_space_percent_used >= 90 and \
               glusterfs_space_percent_used < 95
   

3. From the Salt Master node, apply the changes:

   salt 'I@prometheus:server' state.sls prometheus.server
   

4. Verify the updated alert definition in the Prometheus web UI.

{{ $value }}% of GlusterFS {{ $labels.volume }} volume disk space is used for 2 minutes.

Raises when GlusterFS uses more than 90% of available space. The volume label in the raised alert contains the affected GlusterFS volume.

Typically, you should not change the default value. If the alert is constantly firing, verify the available space on the GlusterFS nodes and adjust the threshold accordingly. In the Prometheus Web UI, use the raise condition query for a longer period of time to define the best threshold.

For example, to change the threshold to 95%:

1. On the cluster level of the Reclass model, create a common file for all alert customizations. Skip this step to use an existing defined file.

   1. Create a file for alert customizations:

      touch cluster/<cluster_name>/stacklight/custom/alerts.yml
      

   2. Define the new file in cluster/<cluster_name>/stacklight/server.yml:

      classes:
      - cluster.<cluster_name>.stacklight.custom.alerts
      ...
      

2. In the defined alert customizations file, modify the alert threshold by overriding the if parameter:

   parameters:
     prometheus:
       server:
         alert:
           GlusterfsSpaceUsedMajor:
             if: >-
               glusterfs_space_percent_used >= 95
   

3. From the Salt Master node, apply the changes:

   salt 'I@prometheus:server' state.sls prometheus.server
   

4. Verify the updated alert definition in the Prometheus web UI.

GlusterFS mount point is not mounted.

Raises when a GlusterFS mount point is not mounted. The path, host, and device labels in the raised alert contain the path, node name, and device of the affected mount point.

Not required