Program
sysdig_program_cpu_cores_used
| |
---|
Prometheus ID | sysdig_program_cpu_cores_used |
Legacy ID | cpu.cores.used |
Metric Type | gauge |
Unit | number |
Description | The 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. |
Additional Notes | |
sysdig_program_cpu_cores_used_percent
| |
---|
Prometheus ID | sysdig_program_cpu_cores_used_percent |
Legacy ID | cpu.cores.used.percent |
Metric Type | gauge |
Unit | percent |
Description | The 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%. |
Additional Notes | |
sysdig_program_cpu_used_percent
| |
---|
Prometheus ID | sysdig_program_cpu_used_percent |
Legacy ID | cpu.used.percent |
Metric Type | gauge |
Unit | percent |
Description | The 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. |
Additional Notes | |
sysdig_program_fd_used_percent
| |
---|
Prometheus ID | sysdig_program_fd_used_percent |
Legacy ID | fd.used.percent |
Metric Type | gauge |
Unit | percent |
Description | The percentage of used file descriptors out of the maximum available. |
Additional Notes | Usually, 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
| |
---|
Prometheus ID | sysdig_program_file_error_open_count |
Legacy ID | file.error.open.count |
Metric Type | counter |
Unit | number |
Description | The number of errors caused by opening files. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_file_error_total_count |
Legacy ID | file.error.total.count |
Metric Type | counter |
Unit | number |
Description | The number of error caused by file access. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_file_in_bytes |
Legacy ID | file.bytes.in |
Metric Type | counter |
Unit | data |
Description | The number of bytes read from file. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_file_in_iops |
Legacy ID | file.iops.in |
Metric Type | counter |
Unit | number |
Description | The number of file read operations per second. |
Additional Notes | This 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
| |
---|
Prometheus ID | sysdig_program_file_in_time |
Legacy ID | file.time.in |
Metric Type | counter |
Unit | time |
Description | The time spent in file reading. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_file_open_count |
Legacy ID | file.open.count |
Metric Type | counter |
Unit | number |
Description | The number of time the file has been opened. |
Additional Notes | |
sysdig_program_file_out_bytes
| |
---|
Prometheus ID | sysdig_program_file_out_bytes |
Legacy ID | file.bytes.out |
Metric Type | counter |
Unit | data |
Description | The number of bytes written to file. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_file_out_iops |
Legacy ID | file.iops.out |
Metric Type | counter |
Unit | number |
Description | The number of file write operations per second. |
Additional Notes | This 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
| |
---|
Prometheus ID | sysdig_program_file_out_time |
Legacy ID | file.time.out |
Metric Type | counter |
Unit | time |
Description | The time spent in file writing. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_file_total_bytes |
Legacy ID | file.bytes.total |
Metric Type | counter |
Unit | data |
Description | The number of bytes read from and written to file. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_file_total_iops |
Legacy ID | file.iops.total |
Metric Type | counter |
Unit | number |
Description | The number of read and write file operations per second. |
Additional Notes | This 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
| |
---|
Prometheus ID | sysdig_program_file_total_time |
Legacy ID | file.time.total |
Metric Type | counter |
Unit | time |
Description | The time spent in file I/O. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_info |
Legacy ID | info |
Metric Type | gauge |
Unit | number |
Description | |
Additional Notes | |
sysdig_program_memory_used_bytes
| |
---|
Prometheus ID | sysdig_program_memory_used_bytes |
Legacy ID | memory.bytes.used |
Metric Type | gauge |
Unit | data |
Description | The amount of physical memory currently in use. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_memory_used_percent |
Legacy ID | memory.used.percent |
Metric Type | gauge |
Unit | percent |
Description | The percentage of physical memory in use. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_net_connection_in_count |
Legacy ID | net.connection.count.in |
Metric Type | counter |
Unit | number |
Description | The number of currently established client (inbound) connections. |
Additional Notes | This metric is especially useful when segmented by protocol, port or process. |
sysdig_program_net_connection_out_count
| |
---|
Prometheus ID | sysdig_program_net_connection_out_count |
Legacy ID | net.connection.count.out |
Metric Type | counter |
Unit | number |
Description | The number of currently established server (outbound) connections. |
Additional Notes | This metric is especially useful when segmented by protocol, port or process. |
sysdig_program_net_connection_total_count
| |
---|
Prometheus ID | sysdig_program_net_connection_total_count |
Legacy ID | net.connection.count.total |
Metric Type | counter |
Unit | number |
Description | The 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. |
Additional Notes | This metric is especially useful when segmented by protocol, port or process. |
sysdig_program_net_error_count
| |
---|
Prometheus ID | sysdig_program_net_error_count |
Legacy ID | net.error.count |
Metric Type | counter |
Unit | number |
Description | The total number of network errors occurred in a second. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_net_in_bytes |
Legacy ID | net.bytes.in |
Metric Type | counter |
Unit | data |
Description | The number of inbound network bytes. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_net_out_bytes |
Legacy ID | net.bytes.out |
Metric Type | counter |
Unit | data |
Description | The number of outbound network bytes. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_net_request_count |
Legacy ID | net.request.count |
Metric Type | counter |
Unit | number |
Description | The 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. |
Additional Notes | |
sysdig_program_net_request_in_count
| |
---|
Prometheus ID | sysdig_program_net_request_in_count |
Legacy ID | net.request.count.in |
Metric Type | counter |
Unit | number |
Description | The number of inbound network requests. |
Additional Notes | |
sysdig_program_net_request_in_time
| |
---|
Prometheus ID | sysdig_program_net_request_in_time |
Legacy ID | net.request.time.in |
Metric Type | counter |
Unit | time |
Description | The average time to serve an inbound request. |
Additional Notes | |
sysdig_program_net_request_out_count
| |
---|
Prometheus ID | sysdig_program_net_request_out_count |
Legacy ID | net.request.count.out |
Metric Type | counter |
Unit | number |
Description | The number of outbound network requests. |
Additional Notes | |
sysdig_program_net_request_out_time
| |
---|
Prometheus ID | sysdig_program_net_request_out_time |
Legacy ID | net.request.time.out |
Metric Type | counter |
Unit | time |
Description | The average time spent waiting for an outbound request. |
Additional Notes | |
sysdig_program_net_request_time
| |
---|
Prometheus ID | sysdig_program_net_request_time |
Legacy ID | net.request.time |
Metric Type | counter |
Unit | time |
Description | Average time to serve a network request. |
Additional Notes | |
sysdig_program_net_tcp_queue_len
| |
---|
Prometheus ID | sysdig_program_net_tcp_queue_len |
Legacy ID | net.tcp.queue.len |
Metric Type | counter |
Unit | number |
Description | The length of the TCP request queue. |
Additional Notes | |
sysdig_program_net_total_bytes
| |
---|
Prometheus ID | sysdig_program_net_total_bytes |
Legacy ID | net.bytes.total |
Metric Type | counter |
Unit | data |
Description | The total network bytes, including inbound and outbound connections, in a program. |
Additional Notes | By 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
| |
---|
Prometheus ID | sysdig_program_proc_count |
Legacy ID | proc.count |
Metric Type | counter |
Unit | number |
Description | The number of processes on a host or container. |
Additional Notes | |
sysdig_program_syscall_count
| |
---|
Prometheus ID | sysdig_program_syscall_count |
Legacy ID | syscall.count |
Metric Type | gauge |
Unit | number |
Description | The total number of syscalls seen |
Additional Notes | Syscalls are resource intensive. This metric tracks how many have been made by a given process or container |
sysdig_program_thread_count
| |
---|
Prometheus ID | sysdig_program_thread_count |
Legacy ID | thread.count |
Metric Type | counter |
Unit | number |
Description | The total number of threads running in a program. |
Additional Notes | |
sysdig_program_timeseries_count_appcheck
| |
---|
Prometheus ID | sysdig_program_timeseries_count_appcheck |
Legacy ID | metricCount.appCheck |
Metric Type | gauge |
Unit | number |
Description | The number of app check custom metrics. |
Additional Notes | |
sysdig_program_timeseries_count_jmx
| |
---|
Prometheus ID | sysdig_program_timeseries_count_jmx |
Legacy ID | metricCount.jmx |
Metric Type | gauge |
Unit | number |
Description | The number of JMS custom metrics. |
Additional Notes | |
sysdig_program_timeseries_count_prometheus
| |
---|
Prometheus ID | sysdig_program_timeseries_count_prometheus |
Legacy ID | metricCount.prometheus |
Metric Type | gauge |
Unit | number |
Description | The number of Prometheus custom metrics. |
Additional Notes | |
sysdig_program_up
| |
---|
Prometheus ID | sysdig_program_up |
Legacy ID | uptime |
Metric Type | gauge |
Unit | number |
Description | The 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. |
Additional Notes | |