Monitoring and issue reports

You can use the /etc/storpool.conf configuration file to set the cluster name, cluster ID, and other options related to monitoring and debugging.

Cluster name

Required for the pro-active monitoring performed by StorPool Support team. Usually in the <Company-Name>-<City-or-nearest-airport>-<number> form, with numbering starting from 1.

SP_CLUSTER_NAME=StorPool-Sofia-1

Cluster ID

The Cluster ID is a global unique ID assigned by StorPool when licensing the cluster (for example nmjc.b). It consists of two parts a dot between them:

The first part before the dot (nmjc) is the location ID.
The second part after the dot (b) is the sub-cluster ID

Each location consists of one or more clusters.

SP_CLUSTER_ID=nmjc.b

Local user for debug data collection

User to change the ownership of the storpool_abrtsync service runtime (see StorPool services). Unset by default:

SP_ABRTSYNC_USER=

Note

In case of no configuration during installation, this user will be set by default to storpool.

Addresses for sending issue reports

The defaults are shown below. They could be altered (unlikely) in case a jump host or a custom collection nodes are used.

SP_ABRTSYNC_REMOTE_ADDRESSES=reports.storpool.com,reports1.storpool.com,reports2.storpool.com

Deleting local reports

You can use this option to set whether local reports files should be deleted after sync to the remote. Default:1

SP_DELETE_REPORTS=1