One of the most powerful features of Google Stackdriver is it’s visualization capabilities. It is certainly one of the leaders in next-gen visualization and brings the monitoring industry one step closer to observability. So why not use Stackdriver’s superpower on all of the things in your environment? From applications like SAP to databases like Microsoft SQL or on-prem servers, storage, networking and load balancers–Stackdriver can help you trend and troubleshoot it all.
But where should you get started? This blog will walk you through how to build two of our most commonly used Stackdriver dashboards for yourself.
Step 1: Get all your operations data into Stackdriver
The first step to dashboarding is data collection. There are a few ways to go about doing this, but the easiest way to approach this task for Stackdriver is to use Blue Medora BindPlane. This monitoring-integration-as-a-service is free to Google Stackdriver users. Once configured it handles all of your operations data management for nearly 150 different sources through a single, self-maintaining connection. You’ll never have to install and update a bunch of agents or plugins.
To configure your free BindPlane account, visit the Google Cloud Platform Marketplace.
Step 2: Build a single-enivronment dashboard
After you’ve started to bring custom metrics into Stackdriver using BindPlane, you still have to create dashboard content that gives these metrics purpose. One of the best ways to use your new dataset is to create a full-stack dashboard for one or more of your critical applications that are still running on-prem. To get started building your first dashboard in Google Stackdriver:
In Figure 1, I’ve built a full-stack dashboard that includes a Microsoft SQL Server database hosted on VMware vCenter and using Pure Storage. Obviously, your stack will have different types of specific resources, but this list of recommended KPIs is a good baseline to get started in many stacks.
Disk wait time
Average Read/Write Latency
Storage volume metrics
Average Read/Write Latency
Monitoring On-Premises Infrastructure w/ Stackdriver
The above dashboard was built out to represent full visibility into the stack. You should be able to drill down through the stack to understand how our workload is affecting our vCenter host and our storage array. All of this uses the custom metrics being sent from BindPlane into Stackdriver.
Step 3: Build a multi-environment dashboard
After you’ve mastered the full-stack dashboard, you’re ready to move on to dashboarding across hybrid or multi-cloud environments. The good news is that once you’ve figured out how to use BindPlane to simplify your operations data collection process, building the actual dashboard in Stackdriver is very straightforward.
Many large enterprises have applications and services they are planning to migrate to the cloud. And according to research from analyst firm ESG, most organizations are using an app-specific approach to determine their cloud strategy. IT pros are being asked to identify which workloads are best suited for Azure, AWS or on-prem. You can actually use a multi- or hybrid-cloud dashboard to answer that question in Stackdriver. Here’s how:
You should end up with something like Figure 2. This sample dashboard compares the Disk Wait Time for a sample application across a data center, within the Google Cloud Platform and Microsoft Azure.
Load-Test Comparison across Hybrid Cloud Environments
These dashboards are just the start of what you can do when you use BindPlane to pull in metrics and logs from outside the Google Cloud Platform and visualize them within Stackdriver.
Ready to try it yourself? Get started now in the Google Cloud Marketplace.