Home / Edge/ Reference·Windows System Metrics Details

Windows System Metrics Details

Events generated by the Windows Metrics Source include 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 option allows you to include detailed metrics. These are Windows-specific metrics including OS information, system uptime, CPU architecture, etc.

Metrics for the overall system include the following:

NameDescriptionTypeDimensionsMode
windows_cs_logical_processorsNumber of installed logical processors.GaugeN/ABasic
windows_cs_physical_memory_bytesTotal installed physical memory.GaugeN/ABasic
windows_os_infoContains full product name & version in labels.Gaugeproduct, versionBasic
windows_os_physical_memory_free_bytesBytes of physical memory currently unused and available.GaugeN/ABasic
windows_os_processesNumber of process contexts currently loaded or running on the operating system.GaugeN/ABasic
windows_system_processor_queue_lengthNumber of threads in the processor queue.GaugeN/ABasic
windows_system_threadsNumber of Windows system threads.GaugeN/ABasic
windows_cs_hostnameLabeled system hostname information.Gaugehostname, domain, fqdnCustom: Detailed
windows_cpu_infoLabeled CPU information.Gaugearchitecture, device_id, description, family, l2_cache_size, l3_cache_size, nameCustom: Detailed
windows_os_paging_limit_bytesTotal number of bytes that can be stored in the operating system paging files.GaugeN/ACustom: Detailed
windows_os_paging_free_bytesNumber of bytes that can be mapped into the operating system paging files without causing any other pages to be swapped out.GaugeN/ACustom: Detailed
windows_os_processes_limitMaximum number of process contexts the operating system can support.GaugeN/ACustom: Detailed
windows_os_process_memory_limit_bytesMaximum number of bytes of memory that can be allocated to a process.GaugeN/ACustom: Detailed
windows_os_virtual_memory_bytesBytes of virtual memory.GaugeN/ACustom: Detailed
windows_system_exception_dispatches_totalTotal exceptions dispatched by the system.CounterN/ACustom: Detailed
windows_system_system_calls_totalTotal combined calls to Windows NT system service routines by all processes running on the computer.CounterN/ACustom: Detailed
windows_system_system_up_timeTime of last boot of system.GaugeN/ACustom: Detailed

CPU

Basic level captures active, user, system, idle, and iowait percentages over all CPUs.

Custom level toggles the following on or off: Per CPU metrics, Detailed metrics (i.e., metrics for all CPU states), and CPU time metrics (i.e., raw, monotonic CPU time counters).

Metrics for CPUs include the following:

NameDescriptionTypeDimensionsMode
windows_cpu_percent_active_allCPU percent active usageGaugecore, modeBasic
windows_cpu_percent_activeCPU percent active usage per CPUGaugecore, modeBasic or Custom: Per CPU and CPU time metrics
windows_cpu_percentCPU percent active usageGaugecore, mode is set to user, idle, privileged, interrupt, dpcBasic or Custom: Per CPU and CPU time metrics
windows_cpu_parking_statusParking Status represents whether a processor is parked or not.CountercoreBasic or Custom: Per CPU and CPU time metrics
windows_cpu_core_frequency_mhzCore frequency in megahertz.GaugecoreBasic or Custom: Per CPU and CPU time metrics
windows_cpu_time_all_totalSum of all cpu_time across all cores.GaugemodeBasic or Custom: CPU time metrics
windows_cpu_cstate_seconds_totalTime spent in low-power idle state.Countercore, stateCustom: Per CPU and Detailed metrics
windows_cpu_time_totalTime that processor spent in different modes (idle, user, system etc.).Countercore, modeCustom: Per CPU and CPU time metrics
windows_cpu_interrupts_totalTotal number of received and serviced hardware interrupts.CountercoreCustom: Per CPU or Detailed metrics
windows_cpu_dpcs_totalTotal number of received and serviced deferred procedure calls (DPCs).CountercoreCustom: Per CPU or Detailed metrics
windows_cpu_clock_interrupts_totalTotal number of received and serviced clock tick interrupts.CountercoreCustom: Per CPU or Detailed metrics
windows_cpu_idle_break_events_totalTotal number of time processor was woken from idle.CountercoreCustom: Per CPU or Detailed metrics
windows_cpu_processor_performanceAverage performance of the processor while it is executing instructions.Gauge.coreCustom: Per CPU and Detailed metrics
windows_cpu_percent_processor_performanceAverage performance of the processor while it is executing instructions, as a percentage of the nominal performance of the processor.Gauge.coreCustom: Per CPU and Detailed metrics
windows_cpu_percent_processor_utilityAmount of work a processor is completing, as a percentage of the amount of work the processor could complete if it were running at its nominal performance and never idle.Gauge.coreCustom: Per CPU and Detailed metrics
windows_cpu_average_idle_timeProcessor idle time.GaugemodeCustom: Per CPU and Detailed metrics
windows_cpu_percent_privilege_utilityAmount of work a processor is completing while executing in privileged mode.GaugemodeCustom: Per CPU and Detailed metrics
windows_cpu_interrupts_total_per_secTotal number of received and serviced hardware interrupts, computed average on a per second interval.GaugemodeCustom: Per CPU and Detailed metrics
windows_cpu_dpcs_total_per_secTotal number of received and serviced deferred procedure calls (DPCs), computed average on a per second interval.GaugemodeCustom: Per CPU and Detailed metrics
windows_cpu_clock_interrupts_total_per_secTotal number of received and serviced clock tick interrupts, computed average on a per second interval.GaugemodeCustom: Per CPU and Detailed metrics
windows_cpu_idle_break_events_total_per_secTotal number of time processor was woken from idle, computed average on a per second interval.GaugemodeCustom: Per CPU and Detailed metrics
windows_cpu_percent_all_totalCore frequency in megahertz.Gaugemode is set to dpc, idle, interrupt, privilege, user,activeCustom: CPU time metrics

Memory

Basic level captures captures total, used, available, swap_free, and swap_total.

Custom level toggles Detailed metrics on or off. (These are metrics for all memory states.)

Metrics for memory include the following:

NameDescriptionTypeDimensionsMode
windows_memory_available_bytesPhysical memory that is immediately available for allocation to a process or for system use. This is the sum of the standby (cached), free, and zero page lists.GaugeN/ABasic
windows_memory_cache_bytesNumber of bytes currently being used by the filesystem cacheGaugeN/ABasic
windows_memory_cache_bytes_peakMaximum number of CacheBytes after the system was last restarted.GaugeN/ABasic
windows_memory_cache_faults_totalFaults that occur when a page sought in the filesystem cache is not found there and must be retrieved elsewhere in memory (soft fault) or from disk (hard fault).CounterN/ABasic
windows_memory_commit_limitBytes of virtual memory that can be committed without having to extend paging files.GaugeN/ABasic
windows_memory_committed_bytesBytes of committed virtual memory.GaugeN/ABasic
windows_memory_pool_paged_allocs_totalCalls to allocate space in the paged pool, regardless of the amount of space allocated in each call.CounterN/ABasic
windows_memory_pool_paged_bytesNumber of bytes in the paged pool.GaugeN/ABasic
windows_memory_pool_paged_resident_bytesThe size, in bytes, of the portion of the paged pool that is currently resident and active in physical memory. The paged pool is an area of the system virtual memory used for objects that can be written to disk when they are not being used.GaugeN/ABasic
windows_memory_demand_zero_faults_totalNumber of Zeroed pages required to satisfy faults. Windows uses zeroed pages as a security measure to prevent processes from seeing data stored by earlier processes that previously used the memory space.CounterN/ACustom: Detailed
windows_memory_free_and_zero_page_list_bytesPhysical memory allocated to free and zero pages, in bytes. This memory does not contain cached data. It is immediately available for allocation to a process or system use.GaugeN/ACustom: Detailed
windows_memory_free_system_page_table_entriesPage table entries not being used by the system.GaugeN/ACustom: Detailed
windows_memory_modified_page_list_bytesPhysical memory, in bytes, assigned to the modified page list. This memory contains cached data and code that is not actively in use by processes, the system, and the system cache. This memory needs to be written out before it will be available for allocation to a process or for system use.GaugeN/ACustom: Detailed
windows_memory_page_faults_totalOverall rate at which faulted pages are handled by the processor.CounterN/ACustom: Detailed
windows_memory_swap_page_reads_totalDisk page reads (a single read operation reading several pages is still only counted once).CounterN/ACustom: Detailed
windows_memory_swap_pages_read_totalPages read across all page reads (i.e., counting all pages read even if they are read in a single operation).CounterN/ACustom: Detailed
windows_memory_swap_pages_written_totalPages written across all page writes (i.e., counting all pages written even if they are written in a single operation).CounterN/ACustom: Detailed
windows_memory_swap_page_operations_totalTotal number of swap page read and writes (PagesPersec).CounterN/ACustom: Detailed
windows_memory_swap_page_writes_totalDisk page writes (a single write operation writing several pages is still only counted once).CounterN/ACustom: Detailed
windows_memory_pool_nonpaged_allocs_totalThe number of calls to allocate space in the non-paged pool. The non-paged pool is an area of system memory area for objects that cannot be written to disk, and must remain in physical memory as long as they are allocatedCounter.N/ACustom: Detailed
windows_memory_pool_nonpaged_bytesNon-paged pool, in bytes. The non-paged pool is an area of the system virtual memory that is used for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.GaugeN/ACustom: Detailed
windows_memory_standby_cache_core_bytesPhysical memory, in bytes, that is assigned to the core standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system, and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.GaugeN/ACustom: Detailed
windows_memory_standby_cache_normal_priority_bytesPhysical memory, in bytes, that is assigned to the normal priority standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system, and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.GaugeN/ACustom: Detailed
windows_memory_standby_cache_reserve_bytesPysical memory, in bytes, that is assigned to the reserve standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.GaugeN/ACustom: Detailed
windows_memory_system_cache_resident_bytesThe size, in bytes, of the portion of the system file cache which is currently resident and active in physical memory.GaugeN/ACustom: Detailed
windows_memory_system_code_resident_bytesThe size, in bytes, of the pageable operating system code that is currently resident and active in physical memory. This value is a component of Memory/System Code Total Bytes. Memory/System Code Resident Bytes (and Memory/System Code Total Bytes) does not include code that must remain in physical memory and cannot be written to disk.GaugeN/ACustom: Detailed
windows_memory_system_code_total_bytesThe size, in bytes, of the pageable operating system code currently mapped into the system virtual address space. This value is calculated by summing the bytes in Ntoskrnl.exe, Hal.dll, the boot drivers, and filesystems loaded by Ntldr/osloader. This counter does not include code that must remain in physical memory and cannot be written to disk.GaugeN/ACustom: Detailed
windows_memory_system_driver_resident_bytesThe size, in bytes, of the pageable physical memory being used by device drivers. It is the working set (physical memory area) of the drivers. This value is a component of Memory/System Driver Total Bytes, which also includes driver memory that has been written to disk. Neither Memory/System Driver Resident Bytes nor Memory/System Driver Total Bytes includes memory that cannot be written to disk.GaugeN/ACustom: Detailed
windows_memory_system_driver_total_bytesThe size, in bytes, of the pageable virtual memory currently being used by device drivers. Pageable memory can be written to disk when it is not being used. It includes both physical memory (Memory/System Driver Resident Bytes) and code and data paged to disk. It is a component of Memory/System Code Total Bytes.GaugeN/ACustom: Detailed
windows_memory_transition_faults_totalRate at which page faults are resolved, by recovering pages that were being used by another process sharing the page, or were on the modified page list or the standby list, or were being written to disk at the time of the page fault. The pages were recovered without additional disk activity. Transition faults are counted in numbers of faults; because only one page is faulted in each operation, it is also equal to the number of pages faulted.CounterN/ACustom: Detailed
windows_memory_transition_pages_repurposed_totalRate at which the number of transition cache pages were reused for a different purpose. These pages would have otherwise remained in the page cache to provide a (fast) soft fault (instead of retrieving it from backing store) in the event the page was accessed in the future.CounterN/ACustom: Detailed
windows_memory_write_copies_totalThe number of page faults caused by attempting to write that were satisfied by copying the page from elsewhere in physical memory.CounterN/ACustom: Detailed
windows_memory_used_percentPercent of committed memory used.GaugeN/ACustom: Detailed
windows_memory_available_percentPercent of committed memory available.GaugeN/ACustom: Detailed
windows_memory_cache_faults_per_secRate of cache faults computed per sec.GaugeN/ACustom: Detailed
windows_memory_demand_zero_faults_per_secRate of Zeroed pages required to satisfy faults computed per sec.GaugeN/ACustom: Detailed
windows_memory_page_faults_per_secRate at which faulted pages are handled by the processor computed per sec.GaugeN/ACustom: Detailed
windows_memory_page_reads_per_secDisk page reads computed per sec.GaugeN/ACustom: Detailed
windows_memory_pages_input_per_secDisk page reads computed per sec.GaugeN/ACustom: Detailed
windows_memory_pages_output_per_secPages written across all page writes computed per sec.GaugeN/ACustom: Detailed
windows_memory_pages_per_secTotal number of swap page read and writes computed per sec.GaugeN/ACustom: Detailed
windows_memory_page_writes_per_secDisk page writes computed per sec.GaugeN/ACustom: Detailed
windows_memory_transition_faults_secRate at which page faults are resolved computed per sec.GaugeN/ACustom: Detailed
windows_memory_transition_pages_repurposed_per_secRate at which the number of transition cache pages were reused for a different purpose computed per sec.GaugeN/ACustom: Detailed
windows_memory_write_copies_per_secRate at which the number of page faults caused by attempting to write that were satisfied by copying the page from elsewhere in physical memory computed per sec.GaugeN/ACustom: Detailed

Network

Basic level captures bytes, packets, errors, and connections over all interfaces.

Custom level exposes the following:

  • The Interface filter, which specifies which network interfaces to include or exclude. (An empty filter will include all metrics.)
  • Per interface metrics, which toggle on or off.
  • Detailed metrics, which toggle on or off. If on, the Protocol metrics toggle appears, allowing you to choose whether to generate metrics for ICMP, ICMPMsg, IP, TCP, UDP, and UDPLite.

Metrics for networks include the following:

NameDescriptionTypeDimensionsMode
windows_net_packets_outbound_discarded_totalTotal outbound packets to be discarded even though no errors had been detected to prevent transmission.CounternicCustom: Detailed metrics
windows_net_packets_outbound_errors_totalTotal packets that could not be transmitted due to errors.CounternicCustom: Detailed metrics
windows_net_packets_received_discarded_totalTotal inbound packets that were chosen to be discarded even though no errors had been detected to prevent delivery.CounternicCustom: Detailed metrics
windows_net_packets_received_errors_totalTotal packets that could not be received due to errors.CounternicCustom: Detailed metrics
windows_net_packets_received_unknown_totalTotal packets received by interface that were discarded because of an unknown or unsupported protocol.CounternicCustom: Detailed metrics
windows_net_packets_received_non_unicast_totalTotal non-unicast (subnet broadcast or subnet multicast) packets that are delivered to a higher-layer protocol.CounternicCustom: Detailed metrics
windows_net_packets_received_unicast_totalTotal subnet-unicast packets that are delivered to a higher-layer protocol.CounternicCustom: Detailed metrics
windows_net_packets_sent_unicast_totalTotal packets requested to be transmitted to subnet-unicast addresses by higher-level protocols.CounternicCustom: Detailed metrics
windows_net_packets_sent_non_unicast_total_per_secTotal packets that are requested to be transmitted to nonunicast (subnet broadcast or subnet multicast) addresses by higher-level protocols.GaugenicCustom: Detailed metrics
windows_net_bytes_received_totalTotal bytes received by interface.CounternicCustom: Per Interface metrics
wwindows_net_bytes_received_total_per_secTotal bytes received by interface computed per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_bytes_sent_totalTotal bytes transmitted by interface.CounternicCustom: Per Interface metrics
windows_net_bytes_sent_total_per_secTotal bytes transmitted by interface computed per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_bytes_totalTotal bytes received and transmitted by interface.CounternicCustom: Per Interface metrics
windows_net_bytes_total_per_secTotal bytes received and transmitted by interface per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_packets_received_total_per_secTotal packets received by interface computed per sec.CounternicCustom: Per Interface metrics and Detailed metrics
windows_net_bytes_total_per_secTotal bytes received and transmitted by interface per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_packets_received_non_unicast_total_per_secRate at which non-unicast (subnet broadcast or subnet multicast) packets are delivered to a higher-layer protocol computed per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_packets_totalTotal packets received and transmitted by interface.CounternicCustom: Per Interface metrics
windows_net_packets_total_per_secTotal packets received and transmitted by interface computed per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_packets_sent_totalTotal packets transmitted by interface.CounternicCustom: Per Interface metrics
windows_net_packets_sent_total_per_secTotal packets transmitted by interface computed per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_packets_sent_unicast_total_per_secRate at which packets are requested to be transmitted to subnet-unicast addresses by higher-level protocols computed per sec.GaugenicCustom: Per Interface metrics and Detailed metrics
windows_net_packets_sent_non_unicast_totalRate at which packets that are requested to be transmitted to nonunicast (subnet broadcast or subnet multicast) addresses by higher-level protocols per sec.CounternicCustom: Per Interface metrics and Detailed metrics
windows_net_current_bandwidth_bytesEstimate of the interface’s current bandwidth in bytes per second.GaugenicCustom: Detailed metrics
windows_tcp_connection_failures_all_totalNumber of times TCP connections have made a direct transition to the CLOSED state from the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition from the SYN-RCVD state to the LISTEN state.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_connections_active_all_totalNumber of times TCP connections have made a direct transition from the CLOSED state to the SYN-SENT state.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_connections_establishedNumber of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.GaugeafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_connections_passive_all_totalNumber of times TCP connections have made a direct transition from the LISTEN state to the SYN-RCVD state.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_connections_reset_totalNumber of times TCP connections have made a direct transition from the LISTEN state to the SYN-RCVD state.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_totalTotal segments sent or received using the TCP protocol.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_received_all_totalTotal segments received using the TCP protocol.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_retransmitted_all_totalTotal segments retransmitted using the TCP protocol.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_sent_all_totalTotal segments sent using the TCP protocol.CounterafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_all_total_per_secTotal segments sent or received using the TCP protocol computed per sec.GaugeafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_received_all_total_per_secTotal segments received using the TCP protocol computed per sec.GaugeafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_retransmitted_all_total_per_secTotal segments retransmitted using the TCP protocol computed per sec.GaugeafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_tcp_segments_sent_all_total_per_secTotal segments sent using the TCP protocol computed per sec.GaugeafCustom: Detailed and Protocol metrics (TCPv4 and TCPv6)
windows_net_datagrams_all_totalTotal datagrams sent or received using the UDP protocol.CounterafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_no_port_all_totalRate of received UDP datagrams for which there was no application at the destination port.GaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_received_all_totalRate at which UDP datagrams are delivered to UDP users.GaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_received_errors_all_totalNumber of received UDP datagrams that could not be delivered excluding errors due to lack of an application at the destination port.GaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_sent_all_totalTotal UDP datagrams sent from the entity.GaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_no_port_all_total_per_secRate of received UDP datagrams for which there was no application at the destination port computed per secGaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_received_all_total_per_secRate at which UDP datagrams are delivered to UDP users computed per secGaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_received_errors_all_total_per_secRate at which received UDP datagrams that could not be delivered, excluding errors due to lack of an application at the destination port, computed per sec.GaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)
windows_net_datagrams_sent_all_total_per_secRate at which UDP datagrams sent from the entity computed per sec.GaugeafCustom: Detailed and Protocol metrics (UDPv4 and UDPv6)

Disk

Basic level captures disk usage (%), bytes read and written, and read and write operations, over all mounted disks.

Custom level exposes the following:

  • The Volume filter, specifying which Windows volumes to include or exclude. Supports wildcards and ! (not) operators. An empty filter will include all volumes.
  • Per volume metrics, which toggle on or off.
  • Detailed metrics, which toggle on or off.

Metrics for Disk include the following:

NameDescriptionTypeDimensionsMode
windows_logical_disk_requests_queuedOutstanding requests on the disk at the time the performance data is collectedGaugevolumeBasic
windows_logical_disk_read_bytes_totalRate at which bytes are transferred from the disk during read operations.CountervolumeBasic
windows_logical_disk_reads_totalRate of read operations on the disk.CountervolumeBasic
windows_logical_disk_write_bytes_totalRate at which bytes are transferred to the disk during write operations.CountervolumeBasic
windows_logical_disk_writes_totalRate of write operations on the disk.CountervolumeBasic
windows_logical_disk_write_latency_seconds_totalShows the average time, in seconds, of a write operation to the disk.CountervolumeCustom: Detailed metrics
windows_logical_disk_read_latency_seconds_totalShows the average time, in seconds, of a read operation from the disk.CountervolumeCustom: Detailed metrics
windows_logical_disk_read_write_latency_seconds_totalShows the time, in seconds, of the average disk transfer.CountervolumeCustom: Detailed metrics
windows_logical_disk_read_seconds_totalSeconds the disk was busy servicing read request.CountervolumeCustom: Detailed metrics
windows_logical_disk_idle_seconds_totalSeconds the disk was idle (not servicing read/write requests).CountervolumeCustom: Detailed metrics
windows_logical_disk_split_ios_totalNumber of I/Os to the disk split into multiple I/Os.CountervolumeCustom: Detailed metrics
windows_logical_disk_percent_read_timePercent rate of read operations on the disk.GaugevolumeCustom: Detailed metrics
windows_logical_disk_percent_write_timePercent write operations on the disk.GaugevolumeCustom: Detailed metrics
windows_logical_disk_percent_timePercent time the disk was in read + write operationsGaugevolumeCustom: Detailed metrics
windows_logical_disk_percent_timePercent time the disk was idle.GaugevolumeCustom: Detailed metrics
windows_logical_disk_percent_free_spacePercent space free on volume.GaugevolumeCustom: Detailed metrics
windows_logical_disk_average_disk_sec_per_transferMeasures the average time of data reads and writes on the disk.GaugevolumeCustom: Detailed metrics
windows_logical_disk_average_disk_sec_per_readMeasures the average rate of disk read requests that are executed per second on a specific physical disk.GaugevolumeCustom: Detailed metrics
windows_logical_disk_average_disk_sec_per_writeIndicates how fast data is being written on average for a specific logical disk.GaugevolumeCustom: Detailed metrics
windows_logical_disk_split_ios_per_secRate the I/Os to the disk were split into multiple I/Os per sec.GaugevolumeCustom: Detailed metrics
windows_logical_disk_bytes_per_secExposes the rate bytes are transferred to or from the disk during write or read operations per sec.GaugevolumeCustom: Detailed metrics
windows_logical_disk_read_bytes_per_secExposes the rate bytes are transferred to or from the disk during read operations per sec.GaugevolumeCustom: Detailed metrics
windows_logical_disk_reads_per_secExposes the rate of read operations on the disk per sec.GaugevolumeCustom: Detailed metrics
windows_logical_disk_transfers_per_secHow fast data is being read and written for a specific logical disk per sec.GaugevolumeCustom: Detailed metrics
windows_logical_disk_write_bytes_per_seExposes the rate at which bytes are transferred from the disk during write operations per sec.GaugevolumeCustom: Detailed metrics

The windows_logical_disk_free_bytes and windows_logical_disk_size_bytes metrics are not updated in real time and might have a delay of 10-15min. This is the same behavior as the Windows performance counters.

Process Metrics

With Process Metrics enabled, Cribl Edge captures process-specific metrics from Windows 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.

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

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

Process-specific metrics include the following:

NameDescriptionTypeDimensions
process_start_timeTime the process started.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_cpu_time_totalElapsed time that the process’s threads have spent executing instructions in either privileged mode or user mode. Included in this count is code executed to handle some hardware interrupts and trap conditions.counterprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_handlesTotal number of handles the process has open. This number is the sum of the handles currently open by each thread in the process.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_io_bytes_totalTotal number of bytes issued to I/O operations in either read, write, or other mode. This property counts all I/O activity generated by the process to include file, network, and device I/Os. Read and write modes include data operations; other mode includes those that don’t involve data, like control operations.counterprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_io_operations_totalTotal number of I/O operations issued in either read, write, or other mode. This property counts all I/O activity generated by the process to include file, network, and device I/Os. Read and write mode includes data operations; other mode includes those that do not involve data, such as control operations.counterprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_page_faults_totalTotal number of page faults by threads executing in this process. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This can cause the page not to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with which the page is shared.counterprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_page_file_bytesCurrent number of bytes this process has used in the paging files. Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and lack of space in paging files can prevent other processes from allocating memory.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_pool_bytesLast observed number of bytes in the paged or nonpaged pool. The paged pool is an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. The nonpaged pool is an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated. Nonpaged pool bytes are calculated differently than paged pool bytes, so they may not equal the total of paged pool bytes.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_priority_baseCurrent base priority of this process. Threads within a process can raise and lower their own base priority, relative to the process’s base priority.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_private_bytesCurrent number of bytes this process has allocated that can’t be shared with other processes.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_threadsNumber of threads currently active in this process. Every running process has at least one thread.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_virtual_bytesCurrent size, in bytes, of the virtual address space that the process is using. Use of virtual space doesn’t imply use of either disk or main memory pages. Virtual space is finite and when the process uses too much, it can limit its ability to load libraries.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_working_set_private_byteSize of the working set, in bytes, that is used for this process only and not shared or shareable by other processes.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_working_set_peak_bytesMaximum size, in bytes, of the working set of this process at any point in time. The working set is the set of memory pages touched recently by the threads in the process. If free memory is above a threshold, pages are left in the working set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from working sets. If pages are needed, they will be soft-faulted back into the working set before they leave main memory.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name
process_working_set_bytesMaximum number of bytes in the working set of this process at any point in time. If free memory is above a threshold, pages are left in the working set of a process even if they aren’t in use. When free memory falls below a threshold, pages are trimmed from working sets. If pages are needed, they will be soft-faulted back into the working set before they leave main memory.gaugeprocess_set, process_ppid, process_pid, process_cmdline, process_exe_path, process_service_name