e4_computer_engineering.beegfs.mon role – Configure Beegfs Monitoring services
Note
This role is part of the e4_computer_engineering.beegfs collection (version 2.2.0).
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it use: ansible-galaxy collection install e4_computer_engineering.beegfs.
To use it in a playbook, specify: e4_computer_engineering.beegfs.mon.
Entry point main – Configure Beegfs Monitoring services
New in e4_computer_engineering.beegfs 1.0.0
Synopsis
Install and configure Beegfs Monitoring services.
Parameters
Parameter |
Comments |
|---|---|
The location on local filesystem to deploy the connection auth file from Default: |
|
The Beegfs version that will be used https://doc.beegfs.io/latest/release_notes.html Choices:
|
|
The list of interfaces to use by the daemon The interfaces will be written to the file specified in `mgmtd_conn_interfaces_file` Default: |
|
The TCP port at which the management service is responding at This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |
|
The UDP port at which the management service is responding at This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |
|
The name to give to the Influxdb v2 database This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |
|
The name to give to the Influxdb v1 database This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |
|
The port at which the `mon_db_hostname` is responding This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |
|
The network address at which the metrics database service is responding This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |
|
The retention for the data points in Influxdb expressed in the form `^[0-9]+[smhdw]$` This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |
|
The database type where Beegfs monitoring service will ship the metrics This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Choices:
Default: |
|
The password used to connect to the Influxdb v1 instance This option is used and documented in the file /etc/beegfs/beegfs-mon.auth Default: |
|
The username used to connect to the Influxdb v1 instance This option is used and documented in the file /etc/beegfs/beegfs-mon.auth Default: |
|
The organization used to connect to the Influxdb v2 instance This option is used and documented in the file /etc/beegfs/beegfs-mon.auth Default: |
|
The token used to connect to the Influxdb v2 instance This option is used and documented in the file /etc/beegfs/beegfs-mon.auth Default: |
|
Where log entries for the Beegfs monitoring daemon should go This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Choices:
|
|
Whether to populate /etc/hosts file with Beegfs cluster nodes addresses When enabled, all nodes in the inventory will be added to /etc/hosts This is useful when DNS is not available or for testing environments Not executed inside Docker/container environments Choices:
|
|
Send the metrics to the [influxdb_exporter](https://github.com/prometheus/influxdb_exporter) Choices:
|
|
Start the `beegfs-mon.service` Choices:
|
|
The network address at which the Beegfs management service is responding This option is used and documented in the file /etc/beegfs/beegfs-mon.conf Default: |