Integrating Windows into a Unified Monitoring Framework
Introduction
Operating systems are rarely the only option in contemporary IT environments. Cross-platform monitoring that unifies disparate systems into a single framework is necessary to provide true visibility and control. By incorporating a Windows host into the current configuration on Days 8 & 9, I broadened the reach of my monitoring. Through constant monitoring of both the Linux and Windows platforms, this integration made it possible for centralized oversight, streamlined management, and thorough insights into availability and performance throughout the whole infrastructure.
By installing the required tools and protocols, such as granting WMI or SSH access, and configuring the monitoring agent or service to gather and report data, cross-platform monitoring enables you to add and monitor a Windows host.
Objective
Integrating a Linux machine, a Windows server, and a Windows 10 computer into the monitoring system was my objective for Days 8 & 9. I successfully set up communication between the Windows host and the monitoring dashboard, configured the necessary monitoring agent, and confirmed that performance statistics and important system metrics were being appropriately gathered. By adding cross-platform infrastructure support to my monitoring environment, this step increased visibility and ensured operational consistency.
Detailed Procedure
Adding a Linux Machine to the Windows Host Group
Windows server
Configured Windows Firewall to Allow Monitoring
On the Windows Server or Windows 10 machine:
I opened Windows Defender Firewall with Advanced Security.
I navigated to Inbound Rules → New Rule → Custom → ICMPv4-I
I allowed ICMP Echo Requests (Also Known as Pings).
I saved the rule and ensured it was enabled.
Enabled a Service to Monitor (IIS Example)
I opened PowerShell as Administrator. I installed the IIS Web Server:
Install-WindowsFeature -name Web-Server -IncludeManagementTools
I verified IIS by opening a browser on the Windows host:
http://192.168.92.10
Added Windows Host to Uptime Kuma
On the Uptime Kuma dashboard:
I clicked Add New Monitor.
I chose Ping.
Name: Windows Host - Ping
Hostname: 192.168.92.10
Interval: 60 seconds
I clicked Save.
I repeated the process to add an HTTP monitor:
Type: HTTP(s)
Name: Windows Host - IIS
URL: http://192.168.92.10
Verified Monitoring
I returned to the Uptime Kuma Dashboard. Both Ping and HTTP monitors displayed an 'UP' status.
I also opened the IIS default webpage from another machine to confirm accessibility.
Key Activities
- I enabled ICMP (Ping) in Windows Firewall.
- I installed and enabled IIS as a test web service.
- I added Ping and HTTP monitors in Uptime Kuma for the Windows host IP.
Simulation of outage
I turned off the Windows server, and this was the prompt alert notification I got.
Telegram pop-up Alert notification
Up time Kuma Dashboard notification
Windows 10 Monitoring Setup
Configured Windows 10 Firewall to Allow Monitoring
I enabled the File and Printer Sharing (Echo Request – ICMPv4-In) rule in Windows Security → Firewall & Network Protection → Advanced Settings.
This allowed the Windows 10 machine to respond to Ping requests.
In Uptime Kuma, I added a Ping monitor pointing to the Windows 10 IP address.
This confirmed basic “is the host alive?” monitoring.
These are my procedures with screenshots.
I opened Windows Security → Firewall & Network Protection → Advanced Settings.
I enabled ICMP Echo Requests (Ping-In) to allow Uptime Kuma to ping the system.
I confirmed the rule was applied to the active network profile.
Added IIS (HTTP Web Page) for Service Monitoring
I pressed Win + R, typed optionalfeatures, and opened the Windows Features dialog.
I checked Internet Information Services (IIS) and also enabled the IIS Management Console.
I clicked OK, and Windows installed IIS.
I verified IIS by opening a browser on the Windows 10 machine and navigating to: http://192.168.92.142.
I also confirm this by accessing the local host from my laptop's Chrome web browser.
The default IIS landing page was displayed.
In Uptime Kuma, I added a new HTTP(s) monitor with the machine’s IP:
This gave me visibility into whether the Windows 10 host was alive and also serving a web page.
Monitored Another Built-in Service
In addition to Ping and IIS, I configured Uptime Kuma to monitor other built-in Windows 10 services.
SMB Monitoring (TCP 445)
I confirmed file sharing was enabled on the Windows 10 machine and allowed through the firewall.
I opened Control Panel → Network and Sharing Center → Advanced sharing settings.
Under my active network profile, I turned on File and Printer Sharing and Network discovery. I saved the changes.
Allowed SMB Through Windows Firewall
I opened Windows Defender Firewall → Advanced Settings → Inbound Rules.
I located the File and Printer Sharing (SMB-In) rules and enabled them.
Applied it to the correct profiles (Private, Domain, Public).
Verified SMB was Listening Locally
On the Windows 10 machine, I opened PowerShell and ran:
netstat -an | findstr 445
The output showed:
Added SMB Monitor in Uptime Kuma
On the Uptime Kuma dashboard, I clicked Add New Monitor and filled in the details:
Verified the Monitor
On the dashboard, the new SMB monitor switched to UP, confirming that the SMB service was reachable.
Integrating the Windows Host to the status page
Overview of all services status page
Quick Stat
Telegram Alert notification
Conclusion & Success Goal Achieved
Visibility across heterogeneous platforms was successfully increased by integrating a Windows Server and a Windows 10 computer into the current monitoring configuration. I created a unified monitoring framework by turning on firewall rules, setting up IIS as a test service, and confirming connectivity with Ping, HTTP, and SMB monitors.
I implemented IIS web services, enabled ICMP monitoring, and verified other protocols, such as SMB (TCP 445). The outage simulation verified that when the Windows host went down, dashboard updates and alarms functioned as planned.
Centralized control of Linux and Windows servers is now possible with the Uptime Kuma dashboard, and Telegram real-time alerts guarantee prompt outage identification and quicker crisis response. The public status page's inclusion of the Windows hosts improved openness and gave a comprehensive view of the state of the infrastructure.
Success Goal Achieved:
The goal of cross-platform monitoring on Days 8 & 9 was accomplished in full. Through visibility and proactive notifications, the monitoring environment now guarantees operational consistency across many systems, enhances reliability tracking, and boosts stakeholder confidence.
Lessons Learned
- Cross-Platform Consistency: By keeping an eye on both Windows and Linux from the same dashboard, blind spots are decreased, and operational efficiency is increased.
- *Windows Firewall Optimization Is Essential: * Accurate monitoring requires proper firewall configuration (ICMP, SMB, HTTP).
- Deeper understanding of host availability and service health is ensured by combining Ping, HTTP, and TCP tests in multi-layer validation.
- Outage testing strengthens dependability by simulating shutdowns, which confirms real-time warning across several operating systems in addition to detection.
Top comments (0)