Blue Medora provides monitoring and logging services for multiple platforms in a consistent and predictable way. Customers can collect their own data and send it to Cloud Logging and Cloud Monitoring for analysis.
How it works
Blue Medora's Bindplane integrates with Monitoring and Logging, allowing you to capture metrics and logs from parts of your infrastructure that aren't covered by the Monitored resources. These resources include:
- Platforms like Microsoft Azure Compute and VMware vCenter
- Line-of-business applications like Oracle EBS and JBoss
- Database engines like Microsoft SQL Server and OracleDB
Blue Medora sends the metrics to Cloud Monitoring, where you can visualize and analyze this data like any other built-in metrics. These metrics are charged as custom metrics, but there are no additional costs, licenses, or contracts needed to use BindPlane.
In Blue Medora's terms, collectors capture metrics from sources and send the metrics to destinations. Monitoring is one of the available destinations.
Using Blue Medora with Monitoring and Logging involves the following steps:
The Blue Medora collector component runs on each resource you want to monitor. This collector captures metrics from every endpoint you choose to monitor. It also captures metadata about the relationships between the endpoints (for example, “metric is from X database on Y VM”) to allow sorting and filtering.
For more information on collectors, see Collectors: Requirements.
The BindPlane agent is typically installed and configured on the system where the log files exist.
For more information about agents, see the BindPlane agents documentation.
Blue Medora's Bindplane component intercepts and aggregates the data from the individual collectors. Bindplane lets you specify the metrics and logs you are interested in. It preprocesses the data before sending it to Monitoring and Logging. See Destinations: Google Stackdriver for more information.
Bindplane sends the metric data to Cloud Monitoring for ingestion.
When sending data to Monitoring and Logging, Blue Medora refers to Monitoring-provided monitored resources, analogues to Blue Medora's sources.
For details on the metrics collected by Blue Medora for each source, go to the Sources documentation. For general information on the set of endpoints that Blue Medora can monitor, go to the Solutions documentation.
For more information on how BindPlane logging works, refer to the BindPlane logs documentation.
BindPlane architecture and security
Security is an important consideration within the design of the BindPlane solution. Blue Medora is a SOC 2-compliant organization and has passed a Google security audit before partnering with Google to jointly offer this solution.
The architecture and security systems employ strong authentication throughout. Additionally, Blue Medora regularly audits its security practices and performs penetration testing of its systems on a frequent basis.
Example use cases
The following are some of the use cases that are possible using BindPlane.
On-Prem vSphere migration
In this use case, vSphere utilization metrics are gathered to assess what is the total utilization of the vSphere infrastructure. Understanding these baselines are critical to size and monitor moving these workloads to Google Cloud.
For more information on collecting metrics from a VMware vSphere environment, see Blue Medora's VMware vCenter documentation.
Workload monitoring of Microsoft SQL running on Google Cloud
Monitoring provides built-in monitoring for Google Cloud VM metrics. With Bindplane, you can get visibility into the workloads running on Google Cloud.
In this case, a spike in Disk I/O on the Google Cloud VM may indicate a performance issue. With BindPlane monitoring the MSSQL Server, you can trace that disk load down to the specific database instance.
For more information on monitoring a VM running MS SQL Server, see Blue Medora's Microsoft SQL Server documentation.