con_host-substatus-overview.adoc

Host sub-status overview

You can use host sub-statuses in {Project} to see the status of specific areas of a host, such as configuration, build, or content. Sub-statuses feed into the global host status and help you pinpoint what needs attention.

To view the sub-statuses of a host, in the {ProjectWebUI}, navigate to Hosts > All Hosts and click on the host whose full status you want to inspect. You can view the global host status next to the name of the host and the host sub-statuses on the Host status card.

Each sub-status has its own set of possible values that are mapped to the three global status values.

The following sub-statuses are available in {Project}:

Configuration

This sub-status is only relevant if {Project} uses a configuration management system like Ansible, Puppet, or Salt.

Possible values:

Label	Global host status
Alerts disabled	OK
Active	OK
Pending	OK
No changes	OK
No reports	OK / Warning
Out of sync	Warning
Error	Error

Additional information about the values of this sub-status:

• Active: During the last configuration, some resources were applied.

• Pending: During the last configuration, some resources would be applied but your configuration management integration was configured to run in noop mode.

• No changes: During the last configuration, nothing changed.

• No reports: This can be both a Warning or OK status. When there are no reports but the host uses an associated {SmartProxy} for configuration management or the always_show_configuration_status setting is set to true, it maps to Warning. Otherwise it maps to OK.

• Error: This indicates an error during configuration. For example, a configuration run failed to install a package.

• Out of sync: A configuration report was not received within the expected interval, based on the outofsync_interval setting. Reports are identified by an origin and can have different intervals based upon it.

Build

This sub-status is only relevant for hosts provisioned from {Project} or hosts registered through global registration.

Possible values:

Label	Global host status	Number value
Installed	OK	0
Pending installation	OK	1
Token expired	Error	2
Installation error	Error	3

Compliance

Indicates if the host is compliant with OpenSCAP policies.

Possible values:

Label	Global host status	Number value
Compliant	OK	0
Inconclusive	Warning	1
At least one incompliant	Error	2

Execution

Status of the last completed remote execution job.

Possible values:

Label	Global host status	Number value
Last execution succeeded / No execution finished yet	OK	0
Last execution failed	Error	1
Unknown execution status	OK	2 or 3
Last execution cancelled	OK	4

If you want to search for hosts according to their sub-status, use the syntax for searching in {Project} that is outlined in the {AdministeringDocURL}Searching_and_Bookmarking_admin[Searching and Bookmarking] chapter of the Administering {Project} guide, and then build your searches out by using the following status-related examples:

You search for hosts' configuration sub-statuses based on their last reported state.

For example, to find hosts that have at least one pending resource:

status.pending > 0

To find hosts that restarted some service during last run:

status.restarted > 0

To find hosts that have an interesting last run that might indicate something has happened:

status.interesting = true