Red Hat Gluster Storage

Red Hat Gluster Storage

Agent Check Check de l'Agent

Linux OS Supported

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Overview

This check monitors Red Hat Gluster Storage cluster health, volume, and brick status through the Datadog Agent. This GlusterFS integration is compatible with both Red Hat vendored and open-source versions of GlusterFS.

Setup

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.

Installation

The GlusterFS check is included in the Datadog Agent package. No additional installation is needed on your server.

Configuration

  1. Edit the glusterfs.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your GlusterFS performance data. See the sample glusterfs.d/conf.yaml for all available configuration options.

    init_config:
    
     ## @param gstatus_path - string - optional - default: /opt/datadog-agent/embedded/sbin/gstatus
     ## Path to the gstatus command.
     ##
     ## A version of the gstatus is shipped with the Agent binary.
     ## If you are using a source install, specify the location of gstatus.
     #
     # gstatus_path: /opt/datadog-agent/embedded/sbin/gstatus
    
     instances:
       -
         ## @param min_collection_interval - number - optional - default: 60
         ## The GlusterFS integration collects cluster-wide metrics which can put additional workload on the server.
         ## Increase the collection interval to reduce the frequency.
         ##
         ## This changes the collection interval of the check. For more information, see:
         ## https://docs.datadoghq.com/developers/write_agent_check/#collection-interval
         #
         min_collection_interval: 60
    

    NOTE: By default, gstatus internally calls the gluster command which requires running as superuser. Add a line like the following to your sudoers file:

     dd-agent ALL=(ALL) NOPASSWD:/path/to/your/gstatus
    

    If your GlusterFS environment does not require root, set use_sudo configuration option to false.

  2. Restart the Agent.

Log collection

  1. Collecting logs is disabled by default in the Datadog Agent, enable it in your datadog.yaml file:

    logs_enabled: true
    
  2. Edit this configuration block in your glusterfs.d/conf.yaml file to start collecting your GlusterFS logs:

    logs:
      - type: file
        path: /var/log/glusterfs/glusterd.log
        source: glusterfs
      - type: file
        path: /var/log/glusterfs/cli.log
        source: glusterfs
    

Change the path parameter value based on your environment. See the sample conf.yaml for all available configuration options.

  1. Restart the Agent.

See [Datadog’s documentation][6] for additional information on how to configure the Agent for log collection in Kubernetes environments.

Validation

[Run the Agent’s status subcommand][7] and look for glusterfs under the Checks section.

Data Collected

Metrics

glusterfs.brick.block_size
(gauge)
Block Size of brick
Shown as byte
glusterfs.brick.inodes.free
(gauge)
Free inodes in brick
Shown as byte
glusterfs.brick.inodes.total
(gauge)
Total inodes in brick
Shown as byte
glusterfs.brick.inodes.used
(gauge)
Inode used in brick
Shown as byte
glusterfs.brick.online
(gauge)
Number of bricks online
Shown as unit
glusterfs.brick.size.free
(gauge)
Brick size free
Shown as byte
glusterfs.brick.size.total
(gauge)
Total brick size
Shown as byte
glusterfs.brick.size.used
(gauge)
Current bytes used in brick
Shown as byte
glusterfs.cluster.nodes.active
(gauge)
Current active nodes
Shown as node
glusterfs.cluster.nodes.count
(gauge)
Total number of nodes in cluster
Shown as node
glusterfs.cluster.volumes.count
(gauge)
Number of volumes in cluster
Shown as unit
glusterfs.cluster.volumes.started
(gauge)
Number of volumes started in cluster
Shown as unit
glusterfs.subvol.disperse
(gauge)
Disperse count of subvolume
Shown as unit
glusterfs.subvol.disperse_redundancy
(gauge)
Disperse redundancy of subvolume
Shown as unit
glusterfs.subvol.replica
(gauge)
Replicas in subvolume
Shown as unit
glusterfs.volume.bricks.count
(gauge)
Number of bricks in volume
Shown as unit
glusterfs.volume.disperse
(gauge)
Number of dispersed in volume
Shown as unit
glusterfs.volume.disperse_redundancy
(gauge)
Number of disperse redundancy in volume
Shown as unit
glusterfs.volume.distribute
(gauge)
Number of distributed
Shown as unit
glusterfs.volume.inodes.free
(gauge)
Inodes free in volume
Shown as byte
glusterfs.volume.inodes.total
(gauge)
Total size inodes in volume
Shown as byte
glusterfs.volume.inodes.used
(gauge)
Used bytes of inodes in volume
Shown as byte
glusterfs.volume.online
(gauge)
Number of volumes online
Shown as unit
glusterfs.volume.replica
(gauge)
Replicas in volumes
Shown as unit
glusterfs.volume.size.free
(gauge)
Bytes free in volume
Shown as byte
glusterfs.volume.size.total
(gauge)
Bytes total in volume
Shown as byte
glusterfs.volume.size.used
(gauge)
Bytes used in volume
Shown as byte
glusterfs.volume.snapshot.count
(gauge)
number of snapshots of volume
Shown as byte
glusterfs.volume.used.percent
(gauge)
percentage of volume used
Shown as percent

Service Checks

glusterfs.brick.health:
Returns CRITICAL if the sub volume is ‘degraded’. Returns OK if ‘up’.

glusterfs.volume.health:
Returns CRITICAL if the volume is ‘degraded’. Returns OK if ‘up’.

glusterfs.cluster.health:
Returns CRITICAL if the cluster is ‘degraded’. Returns OK otherwise.

Events

GlusterFS does not include any events.

Troubleshooting

Need help? Contact [Datadog support][9].

[6]: [7]: https://docs.datadoghq.com/agent/guide/agent-commands/#agent-status-and-information [8]: https://github.com/DataDog/integrations-core/blob/master/glusterfs/metadata.csv [9]: https://docs.datadoghq.com/help/