Containers

sysdig_container_count

MetadataValue
publicIdsysdig_container_count
legacyIdcontainer.count
descriptionThe count of the number of containers.
notesThis metric is perfect for dashboards and alerts. In particular, you can create alerts that notify you when you have too many (or too few) containers of a certain type in a certain group or node - try segmenting by container.image, .id or .name. See also: host.count.

sysdig_container_cpu_cgroup_used_percent

MetadataValue
publicIdsysdig_container_cpu_cgroup_used_percent
legacyIdcpu.cgroup.used.percent
descriptionThe percentage of a container’s cgroup limit that is actually used. This is the minimum usage for the underlying cgroup limits: cpuset.limit and quota.limit.
notes

sysdig_container_cpu_cores_cgroup_limit

MetadataValue
publicIdsysdig_container_cpu_cores_cgroup_limit
legacyIdcpu.cores.cgroup.limit
descriptionThe number of CPU cores assigned to a container. This is the minimum of the cgroup limits: cpuset.limit and quota.limit.
notes

sysdig_container_cpu_cores_quota_limit

MetadataValue
publicIdsysdig_container_cpu_cores_quota_limit
legacyIdcpu.cores.quota.limit
descriptionThe number of CPU cores assigned to a container. Technically, the container’s cgroup quota and period. This is a way of creating a CPU limit for a container.
notes

sysdig_container_cpu_cores_used

MetadataValue
publicIdsysdig_container_cpu_cores_used
legacyIdcpu.cores.used
descriptionThe CPU core usage of each container is obtained from cgroups, and is equal to the number of cores used by the container. For example, if a container uses two of an available four cores, the value of sysdig_container_cpu_cores_used will be two.
notes

sysdig_container_cpu_cores_used_percent

MetadataValue
publicIdsysdig_container_cpu_cores_used_percent
legacyIdcpu.cores.used.percent
descriptionThe CPU core usage percent for each container is obtained from cgroups, and is equal to the number of cores multiplied by 100. For example, if a container uses three cores, the value of sysdig_container_cpu_cores_used_percent would be 300%.
notes

sysdig_container_cpu_quota_used_percent

MetadataValue
publicIdsysdig_container_cpu_quota_used_percent
legacyIdcpu.quota.used.percent
descriptionThe percentage of a container’s CPU Quota that is actually used. CPU Quotas are a common way of creating a CPU limit for a container. CPU Quotas are based on a percentage of time - a container can only spend its quota of time on CPU cycles across a given time period (default period is 100ms). Note that, unlike CPU Shares, CPU Quota is a hard limit to the amount of CPU the container can use - so this metric, CPU Quota %, should not exceed 100%.
notes

sysdig_container_cpu_shares_count

MetadataValue
publicIdsysdig_container_cpu_shares_count
legacyIdcpu.shares.count
descriptionThe number of CPU shares assigned to a container (technically, the container’s cgroup) - this is a common way of creating a CPU limit for a container. CPU Shares represent a relative weight used by the kernel to distribute CPU cycles across different containers. The default value for a container is 1024. Each container receives its own allocation of CPU cycles, according to the ratio of it’s share count vs to the total number of shares claimed by all containers. For example, if you have three containers, each with 1024 shares, then each will recieve 1/3 of the CPU cycles. Note that this is not a hard limit: a container can consume more than its allocation, if the CPU has cycles that aren’t being consumed by the container they were originally allocated to.
notes

sysdig_container_cpu_shares_used_percent

MetadataValue
publicIdsysdig_container_cpu_shares_used_percent
legacyIdcpu.shares.used.percent
descriptionThe percentage of a container’s allocated CPU shares that are actually used. CPU Shares are a common way of creating a CPU limit for a container. CPU Shares represent a relative weight used by the kernel to distribute CPU cycles across different containers. The default value for a container is 1024. Each container receives its own allocation of CPU cycles, according to the ratio of it’s share count vs to the total number of shares claimed by all containers. For example, if you have three containers, each with 1024 shares, then each will recieve 1/3 of the CPU cycles. Note that this is not a hard limit: a container can consume more than its allocation, if the CPU has cycles that aren’t being consumed by the container they were originally allocated to - so this metric, CPU Shares %, can actually exceed 100%.
notes

sysdig_container_cpu_used_percent

MetadataValue
publicIdsysdig_container_cpu_used_percent
legacyIdcpu.used.percent
descriptionThe CPU usage for each container is obtained from cgroups, and normalized by dividing by the number of cores to determine an overall percentage. For example, if the environment contains six cores on a host, and the container or processes are assigned two cores, Sysdig will report CPU usage of 2/6 * 100% = 33.33%. This metric is calculated differently for hosts and processes.
notes

sysdig_container_fd_used_percent

MetadataValue
publicIdsysdig_container_fd_used_percent
legacyIdfd.used.percent
descriptionThe percentage of used file descriptors out of the maximum available.
notesUsually, when a process reaches its FD limit it will stop operating properly and possibly crash. As a consequence, this is a metric you want to monitor carefully, or even better use for alerts.

sysdig_container_file_error_open_count

MetadataValue
publicIdsysdig_container_file_error_open_count
legacyIdfile.error.open.count
descriptionThe number of errors in opening files.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_file_error_total_count

MetadataValue
publicIdsysdig_container_file_error_total_count
legacyIdfile.error.total.count
descriptionThe number of error caused by file access.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_file_in_bytes

MetadataValue
publicIdsysdig_container_file_in_bytes
legacyIdfile.bytes.in
descriptionThe amount of bytes read from file.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_file_in_iops

MetadataValue
publicIdsysdig_container_file_in_iops
legacyIdfile.iops.in
descriptionThe number of file read operations per second.
notesThis is calculated by measuring the actual number of read and write requests made by a process. Therefore, it can differ from what other tools show, which is usually based on interpolating this value from the number of bytes read and written to the file system.

sysdig_container_file_in_time

MetadataValue
publicIdsysdig_container_file_in_time
legacyIdfile.time.in
descriptionThe time spent in file reading.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_file_open_count

MetadataValue
publicIdsysdig_container_file_open_count
legacyIdfile.open.count
descriptionThe number of time the file has been opened.
notes

sysdig_container_file_out_bytes

MetadataValue
publicIdsysdig_container_file_out_bytes
legacyIdfile.bytes.out
descriptionThe number of of bytes written to file.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_file_out_iops

MetadataValue
publicIdsysdig_container_file_out_iops
legacyIdfile.iops.out
descriptionThe Number of file write operations per second.
notesThis is calculated by measuring the actual number of read and write requests made by a process. Therefore, it can differ from what other tools show, which is usually based on interpolating this value from the number of bytes read and written to the file system.

sysdig_container_file_out_time

MetadataValue
publicIdsysdig_container_file_out_time
legacyIdfile.time.out
descriptionThe time spent in file writing.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_file_total_bytes

MetadataValue
publicIdsysdig_container_file_total_bytes
legacyIdfile.bytes.total
descriptionThe number of bytes read from and written to file.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_file_total_iops

MetadataValue
publicIdsysdig_container_file_total_iops
legacyIdfile.iops.total
descriptionThe number of read and write file operations per second.
notesThis is calculated by measuring the actual number of read and write requests made by a process. Therefore, it can differ from what other tools show, which is usually based on interpolating this value from the number of bytes read and written to the file system.

sysdig_container_file_total_time

MetadataValue
publicIdsysdig_container_file_total_time
legacyIdfile.time.total
descriptionThe time spent in file I/O.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_fs_free_bytes

MetadataValue
publicIdsysdig_container_fs_free_bytes
legacyIdfs.bytes.free
descriptionThe available space in the filesystem.
notes

sysdig_container_fs_free_percent

MetadataValue
publicIdsysdig_container_fs_free_percent
legacyIdfs.free.percent
descriptionThe percentage of free space in the filesystem.
notes

sysdig_container_fs_inodes_total_count

MetadataValue
publicIdsysdig_container_fs_inodes_total_count
legacyIdfs.inodes.total.count
descriptionThe total number of inodes in the filesystem.
notes

sysdig_container_fs_inodes_used_count

MetadataValue
publicIdsysdig_container_fs_inodes_used_count
legacyIdfs.inodes.used.count
descriptionThe number of inodes used in the filesystem.
notes

sysdig_container_fs_inodes_used_percent

MetadataValue
publicIdsysdig_container_fs_inodes_used_percent
legacyIdfs.inodes.used.percent
descriptionThe percentage of inodes usage in the filesystem.
notes

sysdig_container_fs_largest_used_percent

MetadataValue
publicIdsysdig_container_fs_largest_used_percent
legacyIdfs.largest.used.percent
descriptionThe percentage of the largest filesystem in use.
notes

sysdig_container_fs_root_used_percent

MetadataValue
publicIdsysdig_container_fs_root_used_percent
legacyIdfs.root.used.percent
descriptionThe percentage of the root filesystem in use in the container.
notes

sysdig_container_fs_total_bytes

MetadataValue
publicIdsysdig_container_fs_total_bytes
legacyIdfs.bytes.total
descriptionThe size of container filesystem.
notes

sysdig_container_fs_used_bytes

MetadataValue
publicIdsysdig_container_fs_used_bytes
legacyIdfs.bytes.used
descriptionThe used space in the container filesystem.
notes

sysdig_container_fs_used_percent

MetadataValue
publicIdsysdig_container_fs_used_percent
legacyIdfs.used.percent
descriptionThe percentage of the sum of all filesystems in use in the container.
notes

sysdig_container_info

MetadataValue
publicIdsysdig_container_info
legacyIdinfo
descriptionThe info metrics will always have the value of 1.
notes

sysdig_container_memory_limit_bytes

MetadataValue
publicIdsysdig_container_memory_limit_bytes
legacyIdmemory.limit.bytes
descriptionThe memory limit in bytes assigned to a container.
notes

sysdig_container_memory_limit_used_percent

MetadataValue
publicIdsysdig_container_memory_limit_used_percent
legacyIdmemory.limit.used.percent
descriptionThe percentage of memory limit used by a container.
notes

sysdig_container_memory_used_bytes

MetadataValue
publicIdsysdig_container_memory_used_bytes
legacyIdmemory.bytes.used
descriptionThe amount of physical memory currently in use.
notesBy default, this metric shows the average value for the selected scope. For instance, if you apply it to a group of machines, you will see the average value for the whole group. However, the metric can also be segmented by using ‘Segment by’ in the UI.

sysdig_container_memory_used_percent

MetadataValue
publicIdsysdig_container_memory_used_percent
legacyIdmemory.used.percent
descriptionThe percentage of physical memory in use.
notesBy default, this metric shows the average value for the selected scope. For instance, if you apply it to a group of machines, you will see the average value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_memory_virtual_bytes

MetadataValue
publicIdsysdig_container_memory_virtual_bytes
legacyIdmemory.bytes.virtual
descriptionThe virtual memory size of the process, in bytes. This value is obtained from Sysdig events.
notes

sysdig_container_net_connection_in_count

MetadataValue
publicIdsysdig_container_net_connection_in_count
legacyIdnet.connection.count.in
descriptionThe number of currently established client (inbound) connections.
notesThis metric is especially useful when segmented by protocol, port or process.

sysdig_container_net_connection_out_count

MetadataValue
publicIdsysdig_container_net_connection_out_count
legacyIdnet.connection.count.out
descriptionThe number of currently established server (outbound) connections.
notesThis metric is especially useful when segmented by protocol, port or process.

sysdig_container_net_connection_total_count

MetadataValue
publicIdsysdig_container_net_connection_total_count
legacyIdnet.connection.count.total
descriptionThe number of currently established connections. This value may exceed the sum of the inbound and outbound metrics since it represents client and server inter-host connections as well as internal only connections.
notesThis metric is especially useful when segmented by protocol, port or process.

sysdig_container_net_error_count

MetadataValue
publicIdsysdig_container_net_error_count
legacyIdnet.error.count
descriptionThe number of network errors.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_net_http_error_count

MetadataValue
publicIdsysdig_container_net_http_error_count
legacyIdnet.http.error.count
descriptionThe number of failed HTTP requests as counted from 4xx/5xx status codes.
notes

sysdig_container_net_http_request_count

MetadataValue
publicIdsysdig_container_net_http_request_count
legacyIdnet.http.request.count
descriptionThe count of HTTP requests.
notes

sysdig_container_net_http_request_time

MetadataValue
publicIdsysdig_container_net_http_request_time
legacyIdnet.http.request.time
descriptionThe average time taken for HTTP requests.
notes

sysdig_container_net_http_statuscode_error_count

MetadataValue
publicIdsysdig_container_net_http_statuscode_error_count
legacyIdnet.http.statuscode.error.count
descriptionThe number of HTTP error codes returned.
notes

sysdig_container_net_http_statuscode_request_count

MetadataValue
publicIdsysdig_container_net_http_statuscode_request_count
legacyIdnet.http.statuscode.request.count
descriptionThe number of HTTP status codes requests.
notes

sysdig_container_net_http_url_error_count

MetadataValue
publicIdsysdig_container_net_http_url_error_count
legacyIdnet.http.url.error.count
description
notes

sysdig_container_net_http_url_request_count

MetadataValue
publicIdsysdig_container_net_http_url_request_count
legacyIdnet.http.url.request.count
descriptionThe number of HTTP URLs requests.
notes

sysdig_container_net_http_url_request_time

MetadataValue
publicIdsysdig_container_net_http_url_request_time
legacyIdnet.http.url.request.time
descriptionThe time taken for requesting HTTP URLs.
notes

sysdig_container_net_in_bytes

MetadataValue
publicIdsysdig_container_net_in_bytes
legacyIdnet.bytes.in
descriptionThe number of inbound network bytes.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_net_mongodb_error_count

MetadataValue
publicIdsysdig_container_net_mongodb_error_count
legacyIdnet.mongodb.error.count
descriptionThe number of Failed MongoDB requests.
notes

sysdig_container_net_mongodb_request_count

MetadataValue
publicIdsysdig_container_net_mongodb_request_count
legacyIdnet.mongodb.request.count
descriptionThe total number of MongoDB requests.
notes

sysdig_container_net_out_bytes

MetadataValue
publicIdsysdig_container_net_out_bytes
legacyIdnet.bytes.out
descriptionThe number of outbound network bytes.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_net_request_count

MetadataValue
publicIdsysdig_container_net_request_count
legacyIdnet.request.count
descriptionThe total number of network requests. Note, this value may exceed the sum of inbound and outbound requests, because this count includes requests over internal connections.
notes

sysdig_container_net_request_in_count

MetadataValue
publicIdsysdig_container_net_request_in_count
legacyIdnet.request.count.in
descriptionThe number of inbound network requests.
notes

sysdig_container_net_request_in_time

MetadataValue
publicIdsysdig_container_net_request_in_time
legacyIdnet.request.time.in
descriptionThe average time to serve an inbound request.
notes

sysdig_container_net_request_out_count

MetadataValue
publicIdsysdig_container_net_request_out_count
legacyIdnet.request.count.out
descriptionThe number of outbound network requests.
notes

sysdig_container_net_request_out_time

MetadataValue
publicIdsysdig_container_net_request_out_time
legacyIdnet.request.time.out
descriptionThe average time spent waiting for an outbound request.
notes

sysdig_container_net_request_time

MetadataValue
publicIdsysdig_container_net_request_time
legacyIdnet.request.time
descriptionThe average time to serve a network request.
notes

sysdig_container_net_server_connection_in_count

MetadataValue
publicIdsysdig_container_net_server_connection_in_count
legacyIdnet.server.connection.count.in
description
notes

sysdig_container_net_server_in_bytes

MetadataValue
publicIdsysdig_container_net_server_in_bytes
legacyIdnet.server.bytes.in
description
notes

sysdig_container_net_server_out_bytes

MetadataValue
publicIdsysdig_container_net_server_out_bytes
legacyIdnet.server.bytes.out
description
notes

sysdig_container_net_server_total_bytes

MetadataValue
publicIdsysdig_container_net_server_total_bytes
legacyIdnet.server.bytes.total
description
notes

sysdig_container_net_sql_error_count

MetadataValue
publicIdsysdig_container_net_sql_error_count
legacyIdnet.sql.error.count
descriptionThe number of failed SQL requests.
notes

sysdig_container_net_sql_query_error_count

MetadataValue
publicIdsysdig_container_net_sql_query_error_count
legacyIdnet.sql.query.error.count
description
notes

sysdig_container_net_sql_query_request_count

MetadataValue
publicIdsysdig_container_net_sql_query_request_count
legacyIdnet.sql.query.request.count
description
notes

sysdig_container_net_sql_query_request_time

MetadataValue
publicIdsysdig_container_net_sql_query_request_time
legacyIdnet.sql.query.request.time
description
notes

sysdig_container_net_sql_querytype_error_count

MetadataValue
publicIdsysdig_container_net_sql_querytype_error_count
legacyIdnet.sql.querytype.error.count
description
notes

sysdig_container_net_sql_querytype_request_count

MetadataValue
publicIdsysdig_container_net_sql_querytype_request_count
legacyIdnet.sql.querytype.request.count
description
notes

sysdig_container_net_sql_querytype_request_time

MetadataValue
publicIdsysdig_container_net_sql_querytype_request_time
legacyIdnet.sql.querytype.request.time
description
notes

sysdig_container_net_sql_request_count

MetadataValue
publicIdsysdig_container_net_sql_request_count
legacyIdnet.sql.request.count
descriptionThe number of SQL requests.
notes

sysdig_container_net_sql_request_time

MetadataValue
publicIdsysdig_container_net_sql_request_time
legacyIdnet.sql.request.time
descriptionThe average time to complete an SQL request.
notes

sysdig_container_net_sql_table_error_count

MetadataValue
publicIdsysdig_container_net_sql_table_error_count
legacyIdnet.sql.table.error.count
descriptionThe total number of SQL errors returned.
notes

sysdig_container_net_sql_table_request_count

MetadataValue
publicIdsysdig_container_net_sql_table_request_count
legacyIdnet.sql.table.request.count
descriptionThe total number of SQL table requests.
notes

sysdig_container_net_sql_table_request_time

MetadataValue
publicIdsysdig_container_net_sql_table_request_time
legacyIdnet.sql.table.request.time
descriptionThe average time to serve an SQL table request.
notes

sysdig_container_net_tcp_queue_len

MetadataValue
publicIdsysdig_container_net_tcp_queue_len
legacyIdnet.tcp.queue.len
descriptionThe length of the TCP request queue.
notes

sysdig_container_net_total_bytes

MetadataValue
publicIdsysdig_container_net_total_bytes
legacyIdnet.bytes.total
descriptionThe total number of network bytes, including inbound and outbound connections.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_proc_count

MetadataValue
publicIdsysdig_container_proc_count
legacyIdproc.count
descriptionThe number of processes on host or container.
notes

sysdig_container_swap_limit_bytes

MetadataValue
publicIdsysdig_container_swap_limit_bytes
legacyIdswap.limit.bytes
descriptionThe swap limit in bytes assigned to a container.
notes

sysdig_container_swap_limit_used_percent

MetadataValue
publicIdsysdig_container_swap_limit_used_percent
legacyIdswap.limit.used.percent
descriptionThe percentage of swap limit used by the container.
notes

sysdig_container_syscall_count

MetadataValue
publicIdsysdig_container_syscall_count
legacyIdsyscall.count
descriptionThe total number of syscalls seen.
notesSyscalls are resource intensive. This metric tracks how many have been made by a given process or container

sysdig_container_syscall_error_count

MetadataValue
publicIdsysdig_container_syscall_error_count
legacyIdhost.error.count
descriptionThe number of system call errors.
notesBy default, this metric shows the total value for the selected scope. For instance, if you apply it to a group of machines, you will see the total value for the whole group. However, you can easily segment the metric to see it by host, process, container, and so on. Just use ‘Segment by’ in the UI.

sysdig_container_thread_count

MetadataValue
publicIdsysdig_container_thread_count
legacyIdthread.count
descriptionThe number of threads running in a container.
notes

sysdig_container_timeseries_count_appcheck

MetadataValue
publicIdsysdig_container_timeseries_count_appcheck
legacyIdmetricCount.appCheck
descriptionThe number of appcheck custom metrics.
notes

sysdig_container_timeseries_count_jmx

MetadataValue
publicIdsysdig_container_timeseries_count_jmx
legacyIdmetricCount.jmx
descriptionThe number of JMX custom metrics.
notes

sysdig_container_timeseries_count_prometheus

MetadataValue
publicIdsysdig_container_timeseries_count_prometheus
legacyIdmetricCount.prometheus
descriptionThe number of Prometheus custom metrics.
notes

sysdig_container_timeseries_count_statsd

MetadataValue
publicIdsysdig_container_timeseries_count_statsd
legacyIdmetricCount.statsd
descriptionThe number of StatsD custom metrics.
notes

sysdig_container_up

MetadataValue
publicIdsysdig_container_up
legacyIduptime
descriptionThe percentage of time the selected entity was down during the visualized time sample. This can be used to determine if a machine (or a group of machines) went down.
notes


Last modified May 20, 2022