Download PDF
Download page Cisco AppDynamics Hosts.
Cisco AppDynamics Hosts
Cisco Cloud Observability provides data metrics sourced from Splunk AppDynamics (Infrastructure Collector) to provide insight into the host entities running in your private environment.
You must install Host Monitoring to monitor this entity.
Cisco Cloud Observability displays entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.
Detail View
To display the detail view for a Splunk AppDynamics Host instance:
- Navigate to the Observe page.
- Under Infrastructure, click a Hosts group.
The Hosts list view now displays. - Click the Hosts tab to display only Splunk AppDynamics hosts.
- Click a host Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.
Metrics and Key Performance Indicators
Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for hosts.
| Display Name* | Description | Supported OS |
| CPU | ||
CPU Utilization (%) | The percentage of time the CPU was busy processing system or user requests. | Linux, Windows |
CPU (%) | CPU Stolen: The percentage of time a virtual CPU waits for a real CPU while the hypervisor is servicing another virtual processor. | Linux |
CPU IO Wait: The percentage of CPU time that was spent waiting for an I/O request. | Linux | |
CPU System: The percentage of time the CPU was busy processing kernel code. | Linux, Windows | |
CPU User: The percentage of time the CPU was busy processing non-kernel code. | Linux, Windows | |
| Hosts-Infrastructure Machine | ||
|---|---|---|
Load 1, 5, and 15 Minutes (%) | Load 1 Minute: The CPU load presented as an average over the last minute. | Linux, Windows |
| Load 5 Minutes: The CPU load presented as an average over the last 5 minutes. | Linux, Windows | |
| Load 15 Minutes: The CPU load presented as an average over the last 15 minutes. | Linux, Windows | |
| Memory | ||
Memory (MiB) | Memory Available: The amount of memory available for starting new applications without swapping. K indicates 1,000 MiB. | Linux, Windows |
| Memory Total: The total amount of memory. K indicates 1,000 MiB. | Linux, Windows | |
| Memory Used: The amount of memory used. K indicates 1,000 MiB. | Linux, Windows | |
Swap Memory Total and Used (MiB) | Swap Memory Limit: The total amount of allocated swap space. K indicates 1,000 MiB. | Linux, Windows |
| Swap Memory Used: The amount of used swap space. K indicates 1,000 MiB. | Linux, Windows | |
Memory Pages (Count/Sec) | Pages Paged In/Sec: The paging-in rate to memory. | Linux |
| Pages Paged Out/Sec: The paging-out rate from memory. | Linux | |
| Pages Swapped In/Sec: The swapping-in rate of pages to disks. | Linux | |
| Pages Swapped Out/Sec: The swapping-out rate of pages to disks. | Linux | |
| Page Faults/Sec: The number of page faults per second for the system. | Linux | |
Network The Infrastructure Collector does not monitor or report metrics for networks interfaces prefixed with | ||
Network Throughput (KiB/Sec) | Network IO Incoming: The amount of data per second sent by all monitored network devices. | Linux, Windows |
| Network IO Outgoing: The amount of data per second received by all monitored network devices. | Linux, Windows | |
Network Packets (Count/Sec) | Network Incoming: The number of data packets sent per second by all monitored network devices. | Linux, Windows |
| Network Outgoing: The number of data packets received per second by all monitored network devices. | Linux, Windows | |
Network Errors (Count/Min) | Network Incoming: The number of incoming packet errors the network incurs every minute. | Linux, Windows |
| Network Outgoing: The number of outgoing packet errors the network incurs every minute. | Linux, Windows | |
Network Packets Dropped (Count/Sec) | Network Incoming: The number of incoming data packets per second dropped by all monitored network devices. | Linux, Windows |
| Network Outgoing: The number of outgoing data packets per second dropped by all monitored network devices. | Linux, Windows | |
| File System | ||
FileSystem Total and Used (MiB) | FileSystem Total: The amount of storage space available (used and free) across all mount points. On Linux, the space reserved for root is not counted in the available space. K indicates 1,000 MiB. | Linux, Windows |
| FileSystem Used: The amount of storage space in use across all mount points. K indicates 1,000 MiB. | Linux, Windows | |
| Disk | ||
Disk Throughput (KiB/Sec) | Disk Read: The number of KiB per second read from all disks and partitions. | Linux, Windows |
| Disk Written: The number of KiB per second written from all disks and partitions. | Linux, Windows | |
Disk IOPS (Ops/Sec) | Disk Reads: The number of read operations per second performed on all disks and partitions. | Linux, Windows |
| Disk Writes: The number of write operations per second performed on all disks and partitions. | Linux, Windows | |
Average IO Utilization (%) | The average time spent processing read and write requests on all disks and partitions as a percentage of the total reported time period. Databases often report high disk I/O utilization due to frequent read/write requests. For example, if the agent detects read and write processing in 55 out of 60 seconds, the Average IO Utilization for that minute is 92%. This metric does not measure the amount of available disk space or read/write request sizes. | Linux, Windows |
Average Queue Time by Volume (ms) | The time in milliseconds that a read or write request is in the queue before it gets processed across one partition. | Linux |
Kubernetes Node Pressure Kubernetes metrics are only available for Kubernetes setups. Kubernetes metrics are not supported for Host Monitoring setups. | ||
Disk Pressure (0/1) | A value of 1 indicates if kubelet is under pressure due to insufficient disk. | Linux, Windows |
Memory Pressure (0/1) | A value of 1 indicates if kubelet is under pressure due to insufficient memory. | Linux, Windows |
Pid Pressure (0/1) | A value of 1 indicates if kubelet is under pressure due to insufficient number of PIDs. | Linux, Windows |
*Metric Name is not available for Splunk AppDynamics Hosts because this entity uses internal Splunk AppDynamics metrics that are not publicly exposed to users.
Properties
Clicking a Host ID displays the detail view with the Properties panel on the right.
Retention and Purge Time-To-Live (TTL)
For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).
Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.