> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/os-monitoring/windows-server-monitoring.md). # Windows System Monitoring ### Background Monitoring physical servers and virtual machines (VMs) running the Windows Operating System (OS) involves monitoring the availability and performance metrics such as CPU, memory, and disk utilization. It is crucial to have monitoring in place to ensure that systems and applications running on these servers and VMs are healthy and running without problems. After a windows system has been successfully registered in IT-Conductor for monitoring, you will be able to view the Availability, Available Memory, CPU, and Disk or Filesystem utilizations from the Service Grid.

Figure 1: Windows Systems View in IT-Conductor Service Grid

### Features #### Availability Monitoring Monitoring the availability of Windows systems measures server or VM uptime over a specified period of time. In IT-Conductor, you can easily see the availability of a system by looking at the system grid (See Figure 1). Availability is showing as GREEN which indicates that the system is available. Otherwise, it will show as RED and the 100% availability will change to 0.00%. You can also utilize the Availability Chart to see the historical availability data per system. This is helpful in scenarios where you want to investigate issues related to system availability at a certain point in time.

Figure 2: Windows System Availability Chart

#### **Processor Time** CPU Utilization is a key metric in monitoring the performance of a Windows system. It indicates how much processing power is being utilized. The higher the CPU utilization, the more work is being done by the system and the greater the potential for system instability which is why it's important to track CPU usage. In the Processor Time Chart below, you can see the variations in utilization over a certain period of time.

Figure 3: Processor Time Chart

#### Peak Processor Time In the Peak Processor Time Chart below, you should be able to see the highest utilization recorded at a specific point in time. This chart is useful in situations where you want to investigate why applications are slowing down. If you happen to notice that the data points are constantly above the thresholds you initially set, it’s about time to plan and upgrade the processor.

Figure 4: Peak Processor Time Chart

#### Available Memory Memory utilization is a metric that indicates how much memory is being utilized by all the running services and applications in a server. In IT-Conductor, the available memory and committed memory in use are also seen from the service grid (See Figure 1). If you want to dig deeper and investigate, you can utilize the Available Memory and Committed Memory In Use Charts as seen below.

Figure 5: Available Memory Chart

#### **Committed** Memory In Use

Figure 6: Committed Memory In Use Chart

#### File Systems Free Space Disk utilization is the amount of disk space that is currently being used. Free space is simply the amount of disk space left for use. In IT-Conductor, it is represented in percentage (%) and in megabytes (MB) or gigabytes (GB).

Figure 7: File Systems Free Space in IT-Conductor Service Grid

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/os-monitoring/windows-server-monitoring.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.