Program

sysdig_program_cpu_cores_used

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

sysdig_program_cpu_cores_used_percent

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

sysdig_program_cpu_used_percent

MetadataValue
publicIdsysdig_program_cpu_used_percent
legacyIdcpu.used.percent
descriptionThe CPU usage for each program 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 processes are assigned two cores, Sysdig will report CPU usage of 2/6 * 100% = 33.33%. This metric is calculated differently for hosts and containers.
notes

sysdig_program_fd_used_percent

MetadataValue
publicIdsysdig_program_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_program_file_error_open_count

MetadataValue
publicIdsysdig_program_file_error_open_count
legacyIdfile.error.open.count
descriptionThe number of errors caused by 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_program_file_error_total_count

MetadataValue
publicIdsysdig_program_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_program_file_in_bytes

MetadataValue
publicIdsysdig_program_file_in_bytes
legacyIdfile.bytes.in
descriptionThe number 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_program_file_in_iops

MetadataValue
publicIdsysdig_program_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_program_file_in_time

MetadataValue
publicIdsysdig_program_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_program_file_open_count

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

sysdig_program_file_out_bytes

MetadataValue
publicIdsysdig_program_file_out_bytes
legacyIdfile.bytes.out
descriptionThe number 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_program_file_out_iops

MetadataValue
publicIdsysdig_program_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_program_file_out_time

MetadataValue
publicIdsysdig_program_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_program_file_total_bytes

MetadataValue
publicIdsysdig_program_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_program_file_total_iops

MetadataValue
publicIdsysdig_program_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_program_file_total_time

MetadataValue
publicIdsysdig_program_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_program_info

MetadataValue
publicIdsysdig_program_info
legacyIdinfo
description
notes

sysdig_program_memory_used_bytes

MetadataValue
publicIdsysdig_program_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_program_memory_used_percent

MetadataValue
publicIdsysdig_program_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_program_net_connection_in_count

MetadataValue
publicIdsysdig_program_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_program_net_connection_out_count

MetadataValue
publicIdsysdig_program_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_program_net_connection_total_count

MetadataValue
publicIdsysdig_program_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_program_net_error_count

MetadataValue
publicIdsysdig_program_net_error_count
legacyIdnet.error.count
descriptionThe total number of network errors occurred in a second.
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_program_net_in_bytes

MetadataValue
publicIdsysdig_program_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_program_net_out_bytes

MetadataValue
publicIdsysdig_program_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_program_net_request_count

MetadataValue
publicIdsysdig_program_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_program_net_request_in_count

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

sysdig_program_net_request_in_time

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

sysdig_program_net_request_out_count

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

sysdig_program_net_request_out_time

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

sysdig_program_net_request_time

MetadataValue
publicIdsysdig_program_net_request_time
legacyIdnet.request.time
descriptionAverage time to serve a network request.
notes

sysdig_program_net_tcp_queue_len

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

sysdig_program_net_total_bytes

MetadataValue
publicIdsysdig_program_net_total_bytes
legacyIdnet.bytes.total
descriptionThe total network bytes, including inbound and outbound connections, in a program.
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_program_proc_count

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

sysdig_program_syscall_count

MetadataValue
publicIdsysdig_program_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_program_thread_count

MetadataValue
publicIdsysdig_program_thread_count
legacyIdthread.count
descriptionThe total number of threads running in a program.
notes

sysdig_program_timeseries_count_appcheck

MetadataValue
publicIdsysdig_program_timeseries_count_appcheck
legacyIdmetricCount.appCheck
descriptionThe number of app check custom metrics.
notes

sysdig_program_timeseries_count_jmx

MetadataValue
publicIdsysdig_program_timeseries_count_jmx
legacyIdmetricCount.jmx
descriptionThe number of JMS custom metrics.
notes

sysdig_program_timeseries_count_prometheus

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

sysdig_program_up

MetadataValue
publicIdsysdig_program_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

sysdig_program_cpu_used_percent

MetadataValue
publicIdsysdig_program_cpu_used_percent
legacyIdcpu.used.percent
descriptionThe CPU usage for each program is obtained from cgroups, and normalized by dividing by the number of cores to determine an overall percentage.
notes

sysdig_program_memory_used_percent

MetadataValue
publicIdsysdig_program_memory_used_percent
legacyIdmemory.used.percent
descriptionThe percentage of swap memory used. By default, this metric displays the average value for the defined scope. For example, if the scope is set to a group of machines, the metric value will be the average value for the whole group.
notes

Last modified June 23, 2022