Applications Manager's Container monitoring tool makes it possible to obtain flawless monitoring process, by tracking a number of container performance metrics.
Current state of the Container. Possible states are 'Running', 'Paused', 'Restarting', 'OOMKilled', 'Dead'.
Last exit code of Docker Container.
Latest start time of the Container.
Last time the Container had stopped.
Number of times the container has restarted.
CPU and Memory Usage:
The percentage of CPU utilized. In multi core machines, CPU utilization's value can be greater than 100.
The percentage of memory utilized.
Total number of processors available.
Total memory used by the Container (in MB).
Memory limit of the Container (in MB).
|1||Bytes Received||Total number of bytes received by the Container interfaces.|
|2||Bytes Transmitted||Total number of bytes transmitted by the Container interfaces.|
|3||I/O Read||Number of IOs read to/from the disk by the Container.|
|4||I/O write||Number of IOs written to/from the disk by the Container.|
|5||I/O Total||Number of IOs completed to/from the disk by the Container.|
|6||tx-packets Dropped||Packets dropped while transmitting data.|
|7||rx-packets Dropped||Packets dropped while receiving data.|
|1||Active File||Cache memory that has been identified as active by the kernel.|
|2||InActive File||Cache memory that has been identified as inactive by the kernel.|
|3||Active Anonymous||The amount of anonymous memory that has been identified as active by the kernel.|
|4||Inactive Anonymous||The amount of anonymous memory that has been identified as inactive by the kernel.|
|5||Cache||The amount of memory used by the processes of this control group.|
|6||Inevictable||The amount of memory that cannot be reclaimed; generally, it will account for memory that has been locked with mlock. It is often used by crypto frameworks to make sure that secret keys and other sensitive material never gets swapped out to disk.|
|7||Page Fault||Total number of page faults of the system.|
|8||Page Major Fault||Total number of major page faults of the system.|
|9||Page In||Each time a page is "charged" (added to the accounting) to a cgroup, pgpin increases.|
|1o||Page Out||When a page is “uncharged” (no longer “billed” to a cgroup), pgpgout increases.|
|1||Container Name||Name of the Container.|
|2||Container Id||Unique Id used to represent the Container.|
|3||Image||Base image used to create the Container.|
|4||Host Name||'Hostname to use for the Container.'|
|5||Process Id||Process Id mapped to the Container.|
|6||Ip Address||Assigned IP address of the Container.|
|7||Mac Address||Assigned Mac address of the Container.|
|8.||User||User associated with the Container.|
|9||Created At||Time when the Container was created.|
|10||Command||Command used while running the Container.|
|11||Path||Path where the command will be executed.|
|12||Ports||Details of all the ports exposed by the Container.|
|13||Port Binding||Details of all the ports exposed by the Container and their mappings with the host.|