spk-logo-tm-2023
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

How to setup basic Windows monitoring with Nagios

windchill features best plm software
Written by SPK Blog Post
Published on August 4, 2011
In my previous blog post, I talked about how to setup NSClient++ for Windows which is very solid Nagios NRPE client. In this post, I’ll describe how to setup some basic checks for your Windows server within Nagios and hopefully give you some ideas on what you should be monitoring on your Windows servers. When it comes to monitoring Windows servers, or servers in general, you should come up with a list of items that must be monitored as well as items that would be nice to know about, but maybe not wake you up at 3am. For SPK, we evaluate these items when setting up remote server monitoring. You need to know quickly if something on your server has failed (server is unreachable) or is going to fail (disk running out space). So, there are 3 basic checks that I always add for every server monitored. They are:
  • Connectivity (ping check)
  • Fixed disk usage (used space)
  • CPU Load
  • System service checks
These 4 items can be broken down in several different items for monitoring, but the premise is that they are crucial for proper server operation. So, how do we put these checks in for a Windows-based server?  I’ve written up a document on how to do that using Nagios and NSClient. Feel free to download it and take a look. Also, feel free to ask questions, I’ll be more than happy to respond. Subscribe to our blog for useful How To documents and industry tech tips related to IT infrastructure, Engineering Applications,  software engineering tools and methods, and other topics of interest. Bradley Tinder Systems Integrator, SPK and Associates

Latest White Papers

Introducing Atlassian’s Service Collection

Introducing Atlassian’s Service Collection

Are you looking for new tools that empower your teams to deliver exceptional service experiences? Atlassian’s Service Collection ensures great service for both employees and customers. What You Will Learn In the following eBook, you will discover: The tools and...

Related Resources

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

Key takeaways Faster engineering does not always require more headcount: Disconnected systems, manual handoffs, rework, and poor visibility often create more delays than a lack of engineering capacity. A digital thread can eliminate major sources of wasted time:...

Why Late-Stage Changes Are Killing Your Time to Market

Why Late-Stage Changes Are Killing Your Time to Market

Key Takeaways Late-stage changes get expensive fast: The farther a problem travels through design, testing, and manufacturing, the more time, cost, and rework it creates. Disconnected systems and weak traceability are major causes: When requirements, design, software,...

The Engineering Digital Thread Playbook

The Engineering Digital Thread Playbook

In many organizations, systems operate independently, creating a large visibility problem. A digital thread addresses this by creating a connected flow of product information across the lifecycle. This playbook explains why engineering visibility matters, and how...