06.04.20

The Value of Correlation

Why Correlation?

Data that is static or that behaves the same way day-to-day isn’t indicating aberrant behavior. Looking at the correlation of data from today with data from yesterday can tell you if today is different in some way: positive correlation means today is related to yesterday, particularly if deviation is high. Negative correlation with high variability means that today isn’t like yesterday at all. 

Is something going wrong?

One of the problems you have when looking at operational data is that frequently, it’s not really obvious when something is going wrong. If you are within normal parameters, i.e.,  simple thresholds haven’t been crossed, then what can you tell about how a system is performing today? Read More

02.27.19

4 Tips To Monitor Modern Cloud-based Applications & Infrastructure

Modern cloud-based application and infrastructure monitoring is a moving target. And it is one that very much depends on how “native” your cloud application is.

Here is a list of monitoring metrics capabilities you should look for that pertain to time series and events:

1. Some way to track throughput
It can be as simple as counts of requests or transactions processed. This will vary a lot depending upon your use case—do you log requests, transactions, use queues, etc? At a minimum, you should be able to get that data on a fairly frequent basis and then graph it for context. 

2. Storage monitoring
Storage is elastic, but that doesn’t mean you shouldn’t watch how much is getting stored. Simple errors like forgetting to reset a debug flag on a log can quickly consume many gigabytes. RDS in EC2, for example, can tell you how much data is committed—you should watch for it to peak when you don’t expect it. 

3. Health checks on micro-services
Most frameworks for micro-services are capable of telling you with a simple query whether they are healthy. In the cloud, that’s often available in the API of the cloud services manager. Your micro-services (or meshed services) should be able to check in or be checked, and your monitoring tool should have a way to do that. 

4. A threshold on backlog of transactions
Referring back to #1, it’s not only important to track throughput, but you should also track backlog. It will tell you when you need more resources faster than any detailed measurement from deeper in the apps. 

There are many other monitoring metrics to consider, but these four are the ones that we’ve seen most commonly bite customers as they’ve moved to cloud-based monitoring.

12.22.16

How To Set Up Trend Graphs & Personalize Your Login

Thank you to our customers for making 2016 another great year. As our holiday gift to you, GroundWork Monitor 7.1.1 is now available for download. We’ll be kicking off 2017 with an in-depth webinar to introduce its features and enhancements. Plus, check out two nifty tech tips on how to personalize your GroundWork login screen and how to set up trend graphs.

Read More

11.28.16

How To Auto-Generate Service Groups

As 2016 winds down, we want to take a moment to give you a useful tech tip that shows you how to create service groups automatically.

Read More

10.29.16

How To Build SNMP Traps in GroundWork

This month, we have a tech tip that will show you how to perform SNMP traps with GroundWork. We’re also gearing up for GroundWork Monitor 7.1.1 release. There’s still time to register for our 7.1.1 demonstration on Thursday, October 27th, to learn more about its features. And if you’re looking to improve your monitoring expertise, there’s still one more Sys Admin Training this year.

Read More

05.28.16

Network Monitoring With Netflow

We’re back with another edition of our monthly newsletter for customers, partners, and anyone interested in GroundWork’s monitoring technologies. May has been a busy month for us following up interest in our monitoring solution after OpenStack Summit. We learned a lot, and we’re preparing some new treats for our customers who use OpenStack and need to improve their monitoring. Look for updates this summer! We also wanted to let you know what events we will be at this summer (is it almost June already?), and to talk a little bit about the kinds of monitoring technology we are integrating.

Read More

03.30.16

Making A Solid Backup of Your Monitoring Server

Welcome back to another issue of the GroundBreaker, GroundWork’s newsletter for customers and partners. This month, we’re rolling out the next version of GroundWork, 7.1! In our tech tip section, we are looking at you. Specifically at how, with the help a short shell script, you can look like a genius. We’re also looking forward to OpenStack Summit this April in Austin, and Red Hat Summit this June in San Francisco. We hope you can join us!

Read More

02.24.16

Testing the End-User Experience

Welcome back to another issue of the GroundBreaker, GroundWork’s newsletter for customers and partners. This month, we’re looking at the new ElasticStack and how its new features will improve performance and stability for GroundWork users. We also have an exciting announcement about OpenStack Summit. We’ll finish with a short and useful technical tip on end-user experience monitoring of web apps, using recorded javascript you can create in moments.

Read More

01.24.16

Running GroundWork In A Linux Container

Thanks for opening the GroundBreaker, GroundWork’s newsletter for customers and partners. This month we are kicking off 2016 with some commentary on industry trends like how to justify an enterprise monitoring solution. We will finish with a short and useful tech tip on how to run GroundWork on a Linux Container, and how you can use them to run GroundWork servers for testing and even some production monitoring.

Read More