WMI Process (Dashboard, Documentation) (#13910)

docs/collect/system-metrics.md

@@ -37,14 +37,8 @@ can find all system collectors in our [supported collectors list](/collectors/CO
 Netdata is also capable of monitoring Windows systems. The [WMI
 collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/wmi) integrates with
 [windows_exporter](https://github.com/prometheus-community/windows_exporter), a small Go-based binary that you can run
-on Windows systems. The WMI collector then gathers metrics from an endpoint created by windows_exporter.
-
-First, [download windows_exporter](https://github.com/prometheus-community/windows_exporter#installation) and run it
-with the following collectors enabled, changing `0.14.0` to the version you downloaded.
-
-```powershell
-windows_exporter-0.14.0-amd64.exe --collectors.enabled="cpu,memory,net,logical_disk,os,system,logon,tcp"
-```
+on Windows systems. The WMI collector then gathers metrics from an endpoint created by windows_exporter, for more
+details see [the requirements](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/wmi#requirements).
 
 Next, [configure the WMI
 collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/wmi#configuration) to point to the URL

web/gui/dashboard_info.js

@@ -4219,7 +4219,35 @@ netdataDashboard.context = {
     },
 
     // ------------------------------------------------------------------------
-    // WMI
+    // WMI (Process)
+
+    'wmi.processes_cpu_time': {
+        info: 'Total CPU utilization. The amount of time spent by the process in <a href="https://en.wikipedia.org/wiki/CPU_modes#Mode_types" target="_blank">user and privileged</a> modes.'
+    },
+    'wmi.processes_handles': {
+        info: 'Total number of <a href="https://learn.microsoft.com/en-us/windows/win32/sysinfo/handles-and-objects" target="_blank">handles</a> the process has open. This number is the sum of the handles currently open by each thread in the process.'
+    },
+    'wmi.processes_io_bytes': {
+        info: 'Bytes issued to I/O operations in different modes (read, write, other). 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.'
+    },
+    'wmi.processes_io_operations': {
+        info: 'I/O operations issued in different modes (read, write, other). 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.'
+    },
+    'wmi.processes_page_faults': {
+        info: 'Page faults by the 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.'
+    },
+    'wmi.processes_file_bytes': {
+        info: 'Current number of bytes this process has used in the paging file(s). 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.'
+    },
+    'wmi.processes_pool_bytes': {
+        info: 'Pool Bytes is the last observed number of bytes in the paged or nonpaged pool. 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. 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.'
+    },
+    'wmi.processes_threads': {
+        info: 'Number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.'
+    },
+
+    // ------------------------------------------------------------------------
+    // WMI (TCP)
 
     'wmi.tcp_conns_active': {
         info: 'Number of times TCP connections have made a direct transition from the CLOSED state to the SYN-SENT state.'