Troubleshooting Metrics

Troubleshooting metrics include program metrics, connection-level network metrics, and Kubernetes troubleshooting metrics. They are reported on a granular 10s level and are stored for 4 days. Below is the list of troubleshooting metrics and the labels that you can use to segment them.

Program Level Metrics

The following metrics are program metrics:

  • sysdig_program_cpu_cores_used
  • sysdig_program_cpu_cores_used_percent
  • sysdig_program_cpu_used_percent
  • sysdig_program_memory_used_bytes
  • sysdig_program_net_in_bytes
  • sysdig_program_net_out_bytes
  • sysdig_program_net_connection_in_count
  • sysdig_program_net_connection_out_count
  • sysdig_program_net_connection_total_count
  • sysdig_program_net_error_count
  • sysdig_program_net_request_count
  • sysdig_program_net_request_in_count
  • sysdig_program_net_request_out_count
  • sysdig_program_net_request_time
  • sysdig_program_net_request_in_time
  • sysdig_program_net_tcp_queue_len
  • sysdig_program_proc_count
  • sysdig_program_thread_count
  • sysdig_program_up

In addition to the user-defined labels and standard set of labels Sysdig provides, you can use following labels to segment program metrics: program_cmd_line, program_name.

Connection-Level Network Metrics

The following metrics are connection metrics:

  • sysdig_connection_net_in_bytes
  • sysdig_connection_net_out_bytes
  • sysdig_connection_net_total_bytes
  • sysdig_connection_net_connection_in _count
  • sysdig_connection_net_connection_out _count
  • sysdig_connection_net_connection_total _count
  • sysdig_connection_net_request_in_count
  • sysdig_connection_net_request_out_count
  • sysdig_connection_net_request_count
  • sysdig_connection_net_request_in_time
  • sysdig_connection_net_request_out_time
  • sysdig_connection_net_request_time

In addition to the user-defined labels and standard set of labels Sysdig provides, you can use following labels to segment connection level metrics: net_local_service, net_remote_service, net_local_endpoint, net_remote_endpoint, net_client_ip, net_server_ip, net_protocol

Kubernetes Troubleshooting Metrics

The following metrics are Kubernetes troubleshooting metrics:

  • kube_workload_status_replicas_misscheduled
  • kube_workload_status_replicas_scheduled
  • kube_workload_status_replicas_updated
  • kube_pod_container_status_last_terminated_reason
  • kube_pod_container_status_ready
  • kube_pod_container_status_restarts_total
  • kube_pod_container_status_running
  • kube_pod_container_status_terminated
  • kube_pod_container_status_terminated_reason
  • kube_pod_container_status_waiting
  • kube_pod_container_status_waiting_reason
  • kube_pod_init_container_status_last_terminated_reason
  • kube_pod_init_container_status_ready
  • kube_pod_init_container_status_restarts_total
  • kube_pod_init_container_status_running
  • kube_pod_init_container_status_terminated
  • kube_pod_init_container_status_terminated_reason
  • kube_pod_init_container_status_waiting
  • kube_pod_init_container_status_waiting_reason


Last modified May 20, 2022