Welcome to GroundWork Monitor

REDIRECT: This URL has changed to https://support8.gwos.com/gw/gw8/latest/welcome-to-groundwork-monitor
Click the link above if you are not automatically redirected in 10 seconds.

Introduction to GroundWork Monitor 8.1.3

The GroundWork Team is proud to announce yet another new update to GroundWork Monitor, version 8. This is 8.1.3, the 5th version to be released this year, and we have packed this update with many new features and enhancements. You can see the changes from the last version listed in the Release Notes for GroundWork Monitor. If you are new to GroundWork, this article will tell you what you need to know about the product, why we made it, and how to use it.  

Why did we make another version?

We are constantly improving the product, making it easier to use, customize, and scale. We have also been repairing issues we have found, and enhancing the value of the product by offering more features, for the same price, than ever before. We aspire to make a premier monitoring solution that bridges the divide between data center and cloud, between infrastructure and applications. This version is a big step forward.  

What’s the state of this version?

It’s ready to use, and equipped for new monitoring projects with standalone, parent child, primary-standby, and distributed monitoring servers. 

What do I need to know to be able to use GroundWork Monitor 8.1.3?

We are providing a Quick Start document for those of you new to monitoring with GroundWork Monitor 8.1.3. There’s a lot of community knowledge that you can use when setting up GroundWork Monitor, especially if you ever used a prior version. There are also some Docker Commands administrators will want to get familiar with in order to make the most of their GroundWork Monitor 8.1.3 installations, especially if you are new to working with containers. 

What to do, and What not to do

Monitoring is a discipline, with clear benefits to proper implementation, and equally clear downsides to inadequate care and planning. Please see Best Practices.

Related articles