Documentation forSolarWinds Observability SaaS

SolarWinds Observability Agent metrics

Many of the collected metrics from agent entities are displayed as widgets in SolarWinds Observability explorers; additional metrics may be collected and available in the Metrics Explorer. You can also create an alert for when an entity's metric value moves out of a specific range. See Entities in SolarWinds Observability SaaS for information about entity types in SolarWinds Observability SaaS.

The following table lists some of the metrics collected for these entities. To see the self-managed host metrics in the Metrics Explorer, type system. or process. in the search box.

To see a description for a metric which is not in the table, click the metric in the Metrics Explorer and type desc into the Group by field. The metric description will be displayed below the graph. For a complete list of available metrics, see Host Metrics Receiver in the opentelemetry-collector-contrib repository at GitHub.

Metric Units Description
swo.uams.agent.status possible values: ok , updating, update_failed, restarting, disconnected, stopping, jwt_expired

The reported operating status of the Agent

swo.uams.agent.heartbeat  

Reported by the SolarWinds Observability Agent every 1 minute, when it is not reported then may indicate problems with network or the agent.

swo.uams.agent.cpu Percent (%) The average amount of CPU capacity in use, as a percentage
swo.uams.agent.memory Percent (%)

The average amount of memory in use, as a percentage.

swo.uams.agent.diskUsage Percent (%) The amount of storage being used by files and data.
swo.uams.agent.networkIn  

The average amount of data received over the network, in bits.

This metric is not collected for Windows due to operating system limitations.

swo.uams.agent.networkOut

 

The average amount of data send over the network, in bits.

This metric is not collected for Windows due to operating system limitations.

swo.uams.agent.errors.count   The amount of errors from the Agent logs - it is calculated from the recent Agent restart.
swo.uams.agent.uptime   The amount of time from the recent SWO Agent restart.
swo.uams.plugin.cpu   The average amount of CPU used by the plugin, as a percentage .
swo.uams.plugin.memory   The average amount of memory used by the plugin, as a percentage.
swo.uams.plugin.uptime   The amount of time from the recent plugin or SWO Agent restart.
swo.uams.plugin.status   The reported operating status of plugin. See Possible values for plugin status.
swo.uams.plugin.healthy 0,1 It is calculated based on reported operating status of plugin and indicate for problems with plugin.

Possible values for plugin status

Plugin status Healthy metric value Description
STATUS_CODE_OK 1 The plugin is responding via health checks.
STATUS_CODE_STOPPED 0 The plugin process stopped by user, not caused by error.
STATUS_CODE_BROKEN 0 The plugin was not deployed correctly.
STATUS_CODE_START_FAILED 0 The plugin process cannot be started and Agent tries run it in the loop.
STATUS_CODE_NOT_RESPONDING 0 The health check from the plugin process was not received for a defined amount of time but the plugin process is running.
STATUS_CODE_HEALTHCHECK_FAILED 0 Failed to send a health check request to the plugin process.
STATUS_CODE_CONFIGURATION_ISSUE 0 Reported by plugin and it indicates an invalid or missing configuration.
STATUS_CODE_FAILED 0 The plugin process was stopped unexpectedly.
STATUS_CODE_STARTING 0 Start for plugin process was called.
STATUS_CODE_RESTARTING 1 Restart was called.
STATUS_CODE_STOPPING 0 Stop for plugin process was called.
STATUS_CODE_UPDATING 0 Update for plugin was called.
STATUS_CODE_CRITICAL 0 Reported by plugin.
STATUS_CODE_WARNING 0 Reported by plugin.
STATUS_CODE_JWT_EXPIRED 0 It is not possible to refresh JWT.
STATUS_CODE_UPDATE_FAILED 0 Problems with plugin update.
STATUS_CODE_INVALID 0 Unknown reason.