Home / Edge/ Reference·Linux System Metrics Details

Linux System Metrics Details

Events generated by the System Metrics Source have metrics metadata to designate dimension and metric fields. The host field contains the hostname, and is included as a dimension in all of them. The collectors include:

In the Source’s configuration modal, you can set the level of detail for each type of metrics:

  • Basic enables minimal metrics, averaged or aggregated.
  • All enables full, detailed metrics, specified for individual CPUs, interfaces, and so on.
  • Custom displays sub-menus and buttons from which you can choose a level of detail (Basic, All, Custom, or Disabled) for each type of event.
  • Disabled means that no metrics will be generated.

Basic and Custom have different meanings depending on event type and will be described under each section below.

The tables outline the metrics emitted for each mode (Basic or Custom) and where applicable, the dimensions (to indicate where the metrics are coming from).

System

With System Metrics enabled, Cribl Edge captures CPU load averages, uptime, and count. The Custom option allows you to include process metrics that reflect the numbers of processes in various states.

Metrics for the overall system include the following:

NameDescriptionTypeDimensionsMode
node_uname_infoLabeled system information as provided by the uname system call.Counterrelease, sysname,    versionBasic
node_cpu_countThe number of CPU cores.Gaugerelease, sysname, versionBasic
node_uptime_secondsSystem uptime in seconds.CounterN/ABasic
node_boot_time_secondsNode boot time in Unix time.CounterN/ABasic
node_time_secondsSystem time in seconds.CounterN/ABasic
node_load11m load average.GaugeN/ABasic
node_load55m load average.GaugeN/ABasic
node_load1515m load average.GaugeN/ABasic
node_open_fdsOpen file descriptorsCounterN/ABasic
node_processes_state_allTotal number of processes in different states.GaugestateBasic
node_processes_threadsAllocated threads in system.GaugestateBasic
node_procs_blockedNumber of processes blocked waiting for I/O to complete.GaugestateBasic
node_procs_runningNumber of processes in runnable state.GaugestateBasic
node_processes_stateNumber of processes in each state.GaugestateCustom: Process metrics

CPU

Cribl Edge captures active, user, system, idle, and iowait percentages over all CPUs, with options to add per-CPU metrics and raw time counters for each state.

Metrics for CPUs include the following:

NameDescriptionTypeDimensionsMode
node_cpu_percent_active_allPercent all the CPUs spent in activity.GaugeN/ABasic
node_cpu_seconds_active_all_totalSeconds all the CPUs spent in activity (excluding idle and wait).CounterN/ACustom: CPU time metrics
node_cpu_seconds_active_totalSeconds each CPU spent in activity (excluding idle and wait).CountercpuCustom: CPU time metrics
node_cpu_seconds_all_totalSeconds for all CPUs usage.CountermodeCustom: CPU time metrics
node_cpu_seconds_totalSeconds for each CPU’s usage.Countercpu, modeCustom: CPU time metrics
node_cpu_percent_activePercent each CPU spent in activity.GaugecpuCustom: Per CPU or Detailed metrics
node_cpu_percent_allPercent CPU usage for all.Gaugemode,userCustom: Detailed metrics
node_cpu_percentPercent CPU usage for each CPU.Gaugecpu,mode,userCustom: Per CPU or Detailed metrics
  • The Per CPU option adds metrics with the cpu dimension.
  • The Detailed metrics option adds metrics with mode dimension set to: irq, softirq, steal, guest, guest_nice, and nice.

Memory

With System Metrics enabled, Cribl Edge captures memory metrics including total, used, available, swap_free, and swap_total, with the option to toggle all memory states.

Metrics for memory include the following:

NameDescriptionTypeDimensionsMode
node_memory_MemTotal_bytesMemory information field MemTotal_bytes.GaugeN/ABasic
node_memory_Used_bytesUsed memory in bytes.GaugeN/ABasic
node_memory_Used_percentPercent used memory.GaugeN/ABasic
node_memory_MemAvailable_bytesMemory information field MemAvailable_bytes.GaugeN/ABasic
node_memory_MemAvailable_percentPercent memory available.GaugeN/ABasic
node_memory_SwapFree_bytesMemory information field SwapFree_bytes.GaugeN/ABasic
node_memory_SwapTotal_bytesMemory information field SwapTotal_bytes.GaugeN/ABasic
node_vmstat_oom_kill/proc/vmstat information field oom_kill.GaugeN/ABasic
node_vmstat_pgfault/proc/vmstat information field pgfault.GaugeN/ABasic
node_vmstat_pgmajfault/proc/vmstat information field pgmajfault.GaugeN/ABasic
node_vmstat_pgpgin/proc/vmstat information field pgpgin.GaugeN/ABasic
node_vmstat_pgpgout/proc/vmstat information field pgpgout.GaugeN/ABasic
node_vmstat_pswpin/proc/vmstat information field pswpin.GaugeN/ABasic
node_vmstat_pswpout/proc/vmstat information field pswpout.GaugeN/ABasic
node_memory_Active_bytesMemory information field Active_bytes.GaugeN/ACustom: Detailed metrics
node_memory_Buffers_bytesMemory information field Buffers_bytes.GaugeN/ACustom: Detailed metrics
node_memory_Cached_bytesMemory information field Cached_bytes.GaugeN/ACustom: Detailed metrics
node_memory_MemFree_bytesMemory information field MemFree_bytes.GaugeN/ACustom: Detailed metrics
node_memory_SwapCached_bytesMemory information field SwapCached_bytes.GaugeN/ACustom: Detailed metrics

Network

With System Metrics enabled, Cribl Edge captures bytes, packets, errors, and network connections over all interfaces. The Custom option allows you to filter interfaces, and to decide whether to select per-interface metrics and generate protocol metrics.

Metrics for networks include the following:

NameDescriptionTypeDimensionsMode
node_network_receive_bytes_all_totalNetwork device statistic receive_bytes.CounterN/ABasic
node_network_receive_errs_all_totalNetwork device statistic receive_errs.CounterN/ABasic
node_network_receive_packets_all_totalNetwork device statistic receive_packets.CounterN/ABasic
node_network_transmit_bytes_all_totalNetwork device statistic transmit_bytes.CounterN/ABasic
node_network_transmit_errs_all_totalNetwork device statistic transmit_errs.CounterN/ABasic
node_network_transmit_packets_all_totalNetwork device statistic transmit_packets.CounterN/ABasic
node_socket_tcp_established_totalTCP established connections.CounterN/ABasic
node_network_receive_bytes_totalNetwork device statistic receive_bytes per interface.CounterdeviceCustom: Per Interface
node_network_receive_errs_totalNetwork device statistic receive_errs per interface.CounterdeviceCustom: Per Interface
node_network_receive_packets_totalNetwork device statistic receive_packets per interface.CounterdeviceCustom: Per Interface
node_network_transmit_bytes_totalNetwork device statistic transmit_bytes per interface.CounterdeviceCustom: Per Interface
node_network_transmit_errs_totalNetwork device statistic transmit_errs per interface.CounterdeviceCustom: Per Interface
node_network_transmit_packets_totalNetwork device statistic transmit_packets per interface.CounterdeviceCustom: Per Interface
node_network_receive_drop_all_totalNetwork device statistic receive_drop.CounterN/ACustom: Detailed Metrics
node_network_receive_drop_totalNetwork device statistic receive_drop per interface.CounterdeviceCustom: Detailed Metrics
node_network_transmit_drop_all_totalNetwork device statistic transmit_drop.CounterN/ACustom: Detailed Metrics
node_network_transmit_drop_totalNetwork device statistic transmit_drop per interface.CounterdeviceCustom: Detailed Metrics
node_socket_tcp_syn_sent_totalTCP sent packets total.CounterN/ACustom: Detailed Metrics
node_socket_tcp_syn_recv_totalTCP received packets total.CounterN/ACustom: Detailed Metrics
node_socket_tcp_fin_wait1_totalTotal connections waiting for termination request from remote TCP.CounterN/ACustom: Detailed Metrics
node_socket_tcp_fin_wait2_totalActive TCP connections to be shut down.CounterN/ACustom: Detailed Metrics
node_socket_tcp_time_wait_totalLength of time to pass to be sure the remote TCP received the acknowledgement to terminate.CounterN/ACustom: Detailed Metrics
node_socket_tcp_close_totalTotal TCP sockets with closed connections.CounterN/ACustom: Detailed Metrics
node_socket_tcp_last_ack_totalTotal TCP sockets in state before the TCP connection is closed.CounterN/ACustom: Detailed Metrics
node_socket_tcp_listen_totalTotal TCP sockets waiting for a connection request from any remote TCP/port.CounterN/ACustom: Detailed Metrics
node_socket_tcp_closing_totalTotal TCP sockets waiting for connection termination request acknowledgement.CounterN/ACustom: Detailed Metrics
node_socket_tcp_none_totalNumber of TCP sockets with no connections.CounterN/ACustom: Detailed Metrics
node_socket_udp_totalNumber of UDP sockets in use.CounterN/ACustom: Detailed Metrics

Disk

With System Metrics enabled, Cribl Edge captures disk-used metrics – in percent, bytes read and written, and read and write operations – over all mounted disks. The Custom option allows you to filter devices, mountpoint, and filesystem type, and to decide whether to select per-device metrics and generate detailed metrics.

Metrics for Disk include the following:

NameDescriptionTypeDimensionsMode
node_disk_reads_completed_all_totalTotal number of reads completed successfully.CounterN/ABasic
node_disk_read_bytes_all_totalTotal number of bytes read successfully.CounterN/ABasic
node_disk_writes_completed_all_totalNetwork device statistic receive_packets.CounterN/ABasic
node_disk_written_bytes_all_totalTotal number of bytes written successfully.CounterN/ABasic
node_filesystem_size_bytes_allFilesystem size in bytes.GaugeN/ABasic
node_filesystem_avail_bytes_allFilesystem space available to non-root users in bytes.GaugeN/ABasic
node_filesystem_used_bytes_allFilesystem used space in bytes.GaugeN/ABasic
node_filesystem_used_percent_allPercent filesystem used space.GaugeN/ABasic
node_filesystem_files_free_allFilesystem free file nodes.GaugeN/ABasic
node_filesystem_files_used_allFilesystem total used file nodes.GaugeN/ABasic
node_filesystem_files_used_percent_allPercent Filesystem used in all disks.GaugeN/ABasic
node_filesystem_size_bytes_allFilesystem size in bytes.GaugeN/ABasic
node_filesystem_used_bytesFilesystem used space in bytes per disk.Gaugedevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_filesystem_used_percentPercent Filesystem used per disk.Gaugedevice,  fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_reads_completed_totalTotal number of reads completed successfully per disk.CounterdeviceCustom: Per device metrics
node_disk_read_bytes_totalTotal number of bytes read successfully per disk.Counterdevice, fstype, mountpointCustom: Per device metrics
node_disk_writes_completed_totalNetwork device statistic receive_packets per disk.Counterdevice, fstype, mountpointCustom: Per device metrics
node_disk_written_bytes_totalTotal number of bytes written successfully per disk.Counterdevice, fstype, mountpointCustom: Per device metrics
node_disk_discards_completed_all_totalTotal number of discards completed successfully.CounterN/ACustom: Detailed Metrics
node_disk_discards_completed_totalTotal number of discards completed successfully per disk.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_discards_merged_all_totalTotal number of discards merged.CounterN/ACustom:Detailed metrics
node_disk_read_time_seconds_totalTotal number of seconds spent by all reads per disk.Counterdevice, fstype, mountpointCustom:Detailed metrics
node_disk_write_time_seconds_all_totalTotal number of seconds spent by all writes.CounterN/ACustom: Detailed Metrics
node_disk_read_time_seconds_all_totalTotal number of seconds spent by all reads.CounterN/ACustom: Detailed Metrics
node_disk_write_time_seconds_totalTotal number of seconds spent by all writes per disk.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_reads_merged_all_totalTotal number of reads merged.CounterN/ACustom: Detailed Metrics
node_disk_writes_merged_all_totalTotal number of writes merged.CounterN/ACustom: Detailed metrics
node_disk_reads_merged_totalTotal number of reads merged per disk.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_writes_merged_totalTotal number of writes merged per disk.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_discards_merged_totalTotal number of discards merged per disk.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_io_time_seconds_all_totalTotal seconds spent doing I/Os.CounterN/ACustom: Detailed Metrics
node_disk_io_time_seconds_totalTotal seconds spent doing I/Os per disk.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_io_now_allThe number of I/Os currently in progress.GaugeN/ACustom: Detailed Metrics
node_disk_io_nowThe number of I/Os currently in progress per disk.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_disk_io_time_weighted_seconds_all_totalWeighted number of seconds spent doing I/Os per device.Counterdevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_filesystem_size_bytesFilesystem size in bytes per disk.Gaugedevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_filesystem_avail_bytesFilesystem space available to non-root users in bytes per disk.Gaugedevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_filesystem_files_freeFilesystem free file nodes per disk.Gaugedevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_filesystem_files_used_percentPercent Filesystem used per disk.Gaugedevice, fstype, mountpointCustom: Per device metrics or Detailed metrics
node_filesystem_size_bytesFilesystem size in bytes per disk.Gaugedevice, fstype, mountpointCustom: Per device metrics or Detailed metrics

Container

With System Metrics enabled, Cribl Edge generates Docker information with CPU, memory, network, and disk metrics for running containers. Optionally, you can customize which containers to generate metrics from.

Metrics for Container include the following:

NameDescriptionTypeDimensionsMode
container_start_time_secondsUNIX time (seconds since the epoch) when the container was started.CounterN/ABasic
container_finish_time_secondsUNIX time (seconds since the epoch) when the container was stopped. Only for non-running containers.CounterN/ABasic
container_fs_reads_bytes_all_totalTotal bytes read for all disk devices.CounterN/ABasic
container_memory_usage_percentPercent of available memory being used.GaugeN/ABasic
container_network_receive_bytes_all_totalTotal bytes received for all network interfaces.CounterN/ABasic
container_network_receive_errors_all_totalTotal number of errors received for all network interfaces.CounterN/ABasic
container_network_receive_packets_all_totalTotal number of packets received for all network interfaces.CounterN/ABasic
container_network_transmit_bytes_all_totalTotal bytes transmitted for all network interfaces.CounterN/ABasic
container_network_transmit_errors_all_totalTotal number of errors transmitted for all network interfaces.CounterN/ABasic
container_network_transmit_packets_all_totalTotal number of packets transmitted for all network interfaces.CounterN/ABasic
container_memory_total_bytesTotal number of memory bytes available.CounterN/ABasic
container_cpu_user_seconds_totalNumber of seconds the container has been on the CPU running user code.CountercpuCustom: Per device metrics or Detailed metrics
container_cpu_system_seconds_totalNumber of seconds the container has been on the CPU running kernel code.CountercpuCustom: Per device metrics or Detailed metrics
container_fs_reads_bytes_totalTotal bytes read per deviceCounterdeviceCustom: Per device metrics or Detailed metrics
container_fs_writes_bytes_all_totalTotal bytes written for all disk devicesCounterN/ACustom: Detailed metrics
container_fs_writes_bytes_totalTotal bytes written per deviceCounterdeviceCustom: Per device metrics or Detailed metrics
container_fs_reads_all_totalTotal number of read operations for all disk devices.CounterN/ACustom: Detailed metrics
container_fs_writes_totalTotal number write operations per device.CounterdeviceCustom: Per device metrics or Detailed metrics
container_memory_mapped_fileTotal bytes writted for all disk devices.CounterN/ACustom: Detailed metrics
container_memory_max_usage_bytesHighest seen value of the container_memory_usage_bytes metric.CounterN/ACustom: Detailed metrics
container_memory_pginTotal number of memory page-in events.CounterN/ACustom: Detailed metrics
container_mem.pgpgoutTotal number of memory pages paged out.CounterN/ACustom: Detailed metrics
container_memory_pgfaultTotal number of major page faults.CounterN/ACustom: Detailed metrics
container_memory_pgmajfaultTotal number of minor page faults.CounterN/ACustom: Detailed metrics
container_memory_usage_bytesNumber of memory bytes used.CounterN/ACustom: Detailed metrics
container_network_receive_dropped_all_totalTotal number of receives dropped for all network interfaces.CounterN/ACustom: Detailed metrics
container_network_transmit_dropped_all_totalTotal number of transmits dropped for all network interfaces.CounterN/ACustom: Detailed metrics

Process Metrics

With Process Metrics enabled, Cribl Edge captures process-specific metrics from Linux servers and reports them as events. This allows you to monitor specific processes on Cribl.Cloud instances. You can generate events for any process object.

For information on how to configure the System Metrics Source to generate process-specific metrics, check out the Process Metrics section of the System Metrics page.

Process-specific metrics are not affected by the Host Metrics detail setting.

Process-specific metrics include the following:

NameDescriptionTypeDimensions
process_num_threadsThe number of threads.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_open_filedescThe number of file descriptors.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_write_bytesThe number of bytes which this process caused to be sent to the storage layer.Counterprocess_cmdline, process_set, process_uid, process_gid, process_service
process_read_bytesThe number of bytes this process actually fetched from the storage layer. This number is accurate for block-backed filesystems.Counterprocess_cmdline, process_set, process_uid, process_gid, process_service
process_major_page_faultsThe number of major faults for this process that required loading a memory page from disk.Counterprocess_cmdline, process_set, process_uid, process_gid, process_service
process_minor_page_faultsThe number of minor faults for this process that have not required loading a memory page from disk.Counterprocess_cmdline, process_set, process_uid, process_gid, process_service
process_voluntary_context_switchesThe number of voluntary context switches.Counterprocess_cmdline, process_set, process_uid, process_gid, process_service
process_nonvoluntary_context_switchesThe number of involuntary context switches.Counterprocess_cmdline, process_set, process_uid, process_gid, process_service
process_cpu_usageThe process’s CPU usage, expressed as a percentage of total CPU power.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_cpu_secondsThe process’s CPU usage, based on user time and system time.Counterprocess_cmdline, process_set, process_uid, process_gid, process_service
process_resident_memory_bytesThe amount of memory used, in bytes. Includes the pages that count toward text, data, or stack space. Does not include pages that haven’t been demand-loaded in or are swapped out.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_virtual_memory_bytesThe process’s virtual memory size.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_swapped_memory_bytesThe process’s swapped memory size.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_memory_bytesThe total amount of memory used by the process, in bytes.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_memory_usageThe total amount of memory used by the process, as a percentage of total memory.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service
process_start_timeThe time that the process started, derived by adding the start time to the boot time, making it relative to epoch.Gaugeprocess_cmdline, process_set, process_uid, process_gid, process_service