Host Metrics Sumo Logic app
![Thumbnail icon](/img/integrations/hosts-operating-systems/HostMetrics.png)
The Host Metrics app allows you to monitor the performance and resource utilization of hosts and processes that your mission critical applications are dependent upon. Preconfigured dashboards provide insight into CPU, memory, network, file descriptors, page faults, and TCP connectors. This app uses the Sumo Logic installed collector for the collection of host metrics data.
Collecting metrics for the Host Metrics app
This procedure explains how to collect metrics from a host machine and ingest them into Sumo Logic for metrics visualization.
Configure a Collector
Configure an Installed Collector. Collectors can be installed on Linux, Windows, or Mac OS hosts.
Configure a Source
- Configure a Host Metrics Source. Choose Add Source and select Host Metrics as the source type.
- Configure the Source Fields as follows:
- Name. Required. Description is optional. The source name is stored in a searchable field called
_sourceName
. - Source Host. Enter the host name of the machine from which the metrics will be collected.
- Source Category. Required. The Source Category metadata field is a fundamental building block to organize and label Sources. For details, see Best Practices.
- Scan Interval. Select the frequency for the Source to scan for hostmetrics data. Selecting a short interval will increase the message volume and could cause your deployment to incur additional charges. The default is 1 minute.
- Metrics. Select check boxes for the metrics to collect. By default, all CPU and memory metrics are collected. Select the top level check box to select all metrics in that category. A blue checkmark icon indicates that the category is selected. To select individual metrics, click the right-facing arrow to expand the category and select the individual metrics. The icon changes to
, as shown below.
- Name. Required. Description is optional. The source name is stored in a searchable field called
- Click Save.
Metric types
Available metrics include:
- CPU
- Memory
- TCP
- Network
- Disk
The metrics that are collected are described in Host Metrics for Installed Collectors.
Host metrics are gathered by the open-source SIGAR library.
The following tables list the available host metrics.
CPU metrics
Metric | Units | Description |
---|---|---|
CPU_User | % | Total system cpu user time |
CPU_Sys | % | Total system cpu kernel time |
CPU_Nice | % | Total system cpu nice time |
CPU_Idle | % | Total system cpu idle time |
CPU_IOWait | % | Total system cpu IO wait time |
CPU_Irq | % | Total system cpu time servicing interrupts |
CPU_SoftIrq | % | Total system cpu time servicing softirqs |
CPU_Stolen | % | Total system cpu involuntary wait time |
CPU_LoadAvg_1min* | Average | System load average for past 1 minute |
CPU_LoadAvg_5min* | Average | System load average for past 5 minutes |
CPU_LoadAvg_15min* | Average | System load average for past 15 minutes |
CPU_Total | % | Total system CPU usage time |
Load averages are not available on Windows platform.
Memory Metrics
Metric | Units | Description |
Mem_Total | Bytes | Total amount of physical RAM |
Mem_Free | Bytes | The amount of physical RAM left unused by the system |
Mem_Used | Bytes | Total used system memory, calculated as
This metric includes the space allocated in buffers and in the Page Cache, which can make it appear that a larger portion of physical RAM is being consumed than is actually in use. See |
Mem_ActualFree | Bytes | Actual total free system memory calculated as:
Where
|
Mem_ActualUsed | Bytes | Actual total used system memory calculated as: Mem_Total - Mem_Actual_Free This metric better represents the amount of physical RAM in use than Mem_Used . |
Mem_UsedPercent | % | Percent total used system memory calculated as: (Mem_Total - Mem_Actual_Free) / Mem_total |
Mem_FreePercent | % | Percent total free system memory |
Mem_PhysicalRam | Bytes | System random access memory |
TCP metrics
Metric | Units | Description |
---|---|---|
TCP_InboundTotal | Count | TCP inbound connection count |
TCP_OutboundTotal | Count | TCP outbound connection count |
TCP_Established | Count | TCP established connection count |
TCP_Listen | Count | TCP listen connection count |
TCP_Idle | Count | TCP idle connection count |
TCP_Closing | Count | TCP closing connection count |
TCP_CloseWait | Count | TCP close_wait connection count |
TCP_Close | Count | TCP close connection count |
TCP_TimeWait | Count | TCP time_wait connection count |
Networking metrics
These have two additional dimensions:
- Interface: Name of the network interface (example:
eth0
) - Description: Description of the network interface (example:
Dual Band Wireless-AC 8265
)
Networking metrics are cumulative, so you can use the rate operator to display these metrics as a rate per second. For example: metric=Net_InBytes Interface=eth0 | rate
.
Metric | Units | Description |
---|---|---|
Net_InPackets | Packets | Number of received packets |
Net_OutPackets | Packets | Number of sent packets |
Net_InBytes | Bytes | Number of received bytes |
Net_OutBytes | Bytes | Number of sent bytes |
Disk metrics
Disk metrics have two additional dimensions:
- DevName: Device name, such as the mount name (example:
udev
) - DirName: Directory name, such as the mount directory (example:
/dev
)
Disk_Reads
, Disk_Writes
, Disk_ReadBytes
, and Disk_WriteBytes
are cumulative, so you can use the rate operator to display these metrics as a rate per second. For example: metric=Disk_WriteBytes | rate
.
Metric | Units | Description |
---|---|---|
Disk_Reads | Operations | Number of physical disk reads |
Disk_ReadBytes | Bytes | Number of physical disk bytes read |
Disk_Writes | Operations | Number of physical disk writes |
Disk_WriteBytes | Bytes | Number of physical disk bytes written |
Disk_Queue | Operations | Number of disk queue operations |
Disk_InodesAvailable* | Nodes | Number of free file nodes |
Disk_Used | Bytes | Total used bytes on filesystem |
Disk_UsedPercent | % | Percentage of filesystem space used |
Disk_Available | Bytes | Total available bytes on filesystem |
Disk_InodesAvailable
is not available on Windows platform.
Time Intervals
The time interval determines how frequently the Source is scanned for metrics data. Sumo Logic supports pre-specified time intervals (10 seconds, 15 seconds, 30 seconds, 1 minute, and 5 minutes).
You can also specify a time interval in JSON by using the interval parameter, as follows:
"interval" : 60000
The JSON parameter is in milliseconds. We recommend 60 seconds (60000 ms) or longer granularity. Specifying a shorter interval will increase the message volume and could cause your deployment to incur additional charges.
AWS Metadata
Collectors running on AWS EC2 instances can optionally collect AWS Metadata such as EC2 tags to make it easier to search for Host Metrics. For more information, see AWS Metadata Source for Metrics.
Only one AWS Metadata Source for Metrics is required to collect EC2 tags from multiple hosts.
Installing the Host Metrics app
To install the app, do the following:
- Select App Catalog.
- In the 🔎 Search Apps field, run a search for your desired app, then select it.
- Click Install App.
note
Sometimes this button says Add Integration.
- Click Next in the Setup Data section.
- In the Configure section of your respective app, complete the following fields.
- Key. Select either of these options for the data source.
- Choose Source Category and select a source category from the list for Default Value.
- Choose Custom, and enter a custom metadata field. Insert its value in Default Value.
- Key. Select either of these options for the data source.
- Click Next. You will be redirected to the Preview & Done section.
Post-installation
Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.
Each panel slowly fills with data matching the time range query and received since the panel was created. Results will not immediately be available, but will update with full graphs and charts over time.
Upgrading the Host Metrics app (Optional)
To update the app, do the following:
- Select App Catalog.
- In the Search Apps field, search for and then select your app.
Optionally, you can identify apps that can be upgraded in the Upgrade available section. - To upgrade the app, click Upgrade.
- If the upgrade does not have any configuration or property changes, you will be redirected to the Preview & Done section.
- If the upgrade has any configuration or property changes, you will be redirected to Setup Data page.
- In the Configure section of your respective app, complete the following fields.
- Key. Select either of these options for the data source.
- Choose Source Category and select a source category from the list for Default Value.
- Choose Custom and enter a custom metadata field. Insert its value in Default Value.
- Key. Select either of these options for the data source.
- Click Next. You will be redirected to the Preview & Done section.
- In the Configure section of your respective app, complete the following fields.
Post-update
Your upgraded app will be installed in the Installed Apps folder, and dashboard panels will start to fill automatically.
See our Release Notes changelog for new updates in the app.