Status commands

Status commands allow you to view the Management server status.

Table 1.

Command name	Action	Syntax
stat show analytics all	Displays summary information about the state of the Analytics cluster health, nodes, and indices. For details, see stat show analytics commands.	stat show analytics all
stat show analytics health	Provides a red/yellow/green status indicator for the Analytics cluster's health. For details, see stat show analytics commands.	stat show analytics health
stat show analytics nodes	Describes the Analytics cluster topology and provides a quick picture of performance statistics. For details, see stat show analytics commands.	stat show analytics nodes
stat show analytics indices	Provides an overview view of your indices and their related shards. For details, see stat show analytics commands.	stat show analytics indices
stat show all	Displays system status information, such as: disk usage, memory usage, uptime, and active processes.	stat show all
stat show apiconfig	Runs health tests on the Management server database, and returns the following information: Internal check summary Lists PASS/FAIL information from running Informix verification utilities. All checks must report a status of Pass. Memory segments Shows the amount of RAM, both as a percentage and as an aggregate amount, that the Informix engine is using on the current server. The percentage is compared to its maximum allowed memory that is provided to the virtual machine. Review this to make sure that the Informix engine has enough available RAM. Database spaces Shows how much disk space the Informix engine is using on the current server. Review this to ensure the database engine has enough available disk space. Note that only Primary servers use tempsblobsp, so its output is suppressed on other servers. Online server roles Lists online servers, roles, and database transaction log replication state. Database transaction log replication state is represented by a combination of the LogID and LogPos values. LogID is an indication of which transaction log is currently being used; LogPos is the most recently used position within that log. If you watch these values over time LogPos grows to a preconfigured limit, then LogID is incremented by one and LogPos is reset to zero and begins growing again. Database content changes appear first on the primary servers, and then are copied to HDR and RSS servers. In a healthy configuration, the values for LogID/LogPos on the primary server are quickly reflected on the other servers.	stat show apiconfig [verbose]