Drift detection query flags and configuration coverage

Edit online

Use query flags to control which configuration parameters are collected during drift detection. Each flag enables a specific query module that collects information from the IBM Storage Protect server.

Overview

The sp_server_facts_flags variable controls which configuration parameters are collected during drift detection. You can enable or disable individual query modules by setting the corresponding flag to true or false.

Tip: Enable only the query flags that are relevant to your monitoring requirements to optimize collection performance and reduce data volume.

Available query flags

The following table describes the available query flags and the information that each flag collects:

Flag	Description	Default
q_status	Server status information including server name, version, uptime, ports, and licensing details	`false`
q_monitorsettings	Monitoring thresholds and watchdog flags that control server monitoring behavior	`false`
q_db	Database capacity information including total pages, used pages, free pages, and last backup timestamp	`false`
q_dbspace	Tablespace-level storage usage details for database spaces	`false`
q_log	Active and archive log usage information	`false`
q_domain	Policy domain configuration including domain definitions and settings	`false`
q_copygroup	Backup and archive copygroup retention rules	`false`
q_replrule	Replication rules including source and target server information	`false`
q_devclass	Device class information including device type and capacity	`false`
q_mgmtclass	Management class lifecycle rules and retention values	`false`
q_stgpool	Storage pool definitions and usage statistics	`false`

Configuration considerations

Consider the following information when you configure query flags:

All flags are set to false by default. You must explicitly enable the flags that you want to use.
Enabling multiple flags increases the collection time and data volume. Enable only the flags that are necessary for your monitoring requirements.
Some query flags depend on specific server configurations. For example, q_replrule requires replication to be configured on the server.
Query flags are evaluated during each drift detection run. You can modify the flags between runs to adjust the scope of data collection.

Example configuration

The following example shows a vars.yml file with all query flags enabled:

sp_server_facts_flags:
  q_status: true
  q_monitorsettings: true
  q_db: true
  q_dbspace: true
  q_log: true
  q_domain: true
  q_copygroup: true
  q_replrule: true
  q_devclass: true
  q_mgmtclass: true
  q_stgpool: true

To enable only specific flags, set the required flags to true and leave others as false:

sp_server_facts_flags:
  q_status: true
  q_db: true
  q_stgpool: true
  q_monitorsettings: false
  q_dbspace: false
  q_log: false
  q_domain: false
  q_copygroup: false
  q_replrule: false
  q_devclass: false
  q_mgmtclass: false

Configuration coverage

The drift detection feature monitors a comprehensive set of configuration parameters across multiple domains. The scope of data collection depends on the query flags that you enable.

Covered configuration parameters

The following table describes the configuration domains that are collected and monitored by the drift detection feature:

Category	Parameters	Display information
Server status	query status	Server name, version, uptime, ports, and licensing information
Monitoring	query monitorsettings	Thresholds, intervals, and watchdog flags
Database	query db, query dbspace	Database capacity and tablespace usage
Logs	query log	Active and archive log usage
Policies	query domain, query copygroup	Domain configuration and retention rules
Replication	query replrule	Replication source and target information
Storage	query devclass, query stgpool	Device classes and storage pools
Management	query mgmtclass	Lifecycle rules and retention values
System	Hostnames, FQDN, OS metadata	System identity, OS version, and kernel information
Hardware	CPU, memory, disk layout	Hardware summary and resource information
Network	IP addresses, interfaces, service ports	Network configuration and connectivity
Components	Installed packages	IBM Storage Protect server and client components
Configuration	Configuration files	Parsed option files (dsm.sys, dsm.opt)
Nodes	Registered nodes	Node metadata and schedules
Storage agents	Agent list	Agent state and configuration
Audit	Alerts, audit logs	Summary indicators and audit information

Parameters not currently covered

The following configuration parameters are not currently collected by the drift detection feature. These parameters might be added in future releases:

Storage rules (STGRULE)
Library infrastructure (LIBRARY)
Directory pools (DIRSPACE)
Replication servers (REPLSERVER)
Peer servers (SERVER)
Retention rules (RETRULE, RETSET)
Volume history (VOLHISTORY)
Enhanced volume information (VOLUME)
Firmware and driver versions
Certificate metadata
Firewall rules

Tip: If you require monitoring for parameters that are not currently covered, contact IBM Support to request feature enhancements.