Cloud Monitoring provides integrations formonitoring third-partyapplications, but support for some of theseintegrations has been deprecated. For information about which integrations weredeprecated, go to thedeprecation guide for third-party integrations.

This guide provides the steps to transition these integrations toBindPlane, asolution provided by Monitoring partner,Blue Medora.

Cloud Monitoring offers BindPlane at no additional cost toMonitoring customers, but metrics collected through BindPlaneare charged at standard custom metric rates. Forinformation on the cost of this added consumption, seeGoogle Cloud Observability pricing.You might also review themanaging your costs section of thisdocument.

About BindPlane from Blue Medora:BindPlane is a service that connects the health, performance data, and logs of over 150 data sources directly into Monitoring. These data sources provide an alternative to the deprecated integrations, as well as adding support for new use cases, such as databases, Microsoft Windows, on-premise or hosted data centers, and hybrid cloud in Azure and AWS. See this video for a quick introduction to BindPlane. For more information about Blue Medora, see About Blue Medora.

Uninstalling the plugin for the third-party integration

Uninstall the plugin for the third-party integration by logging into each hostand removing the configuration for each plugin instance.

Installing the BindPlane integration

The following sections provide details on installing and configuring BindPlanewith Cloud Monitoring.

Creating a BindPlane account

To get started, create anaccount withBindPlane.After receiving an account-verification message, you can continue with theremainder of these procedures.

Connecting BindPlane to Cloud Monitoring

To connect to Monitoring, add a destination. In this case, yourdestination isStackdriver. The most up-to-date information on linking yourMonitoring account with BindPlane can be found atBlue Medora'sguide for configuring a destinationguide.

Installing the BindPlane collector

BindPlane collectorsreside within your network and connect to any data source that you want tomonitor. The collector requires a server with network access to the data sourcesyou're planning to monitor.

Note: To continue sending metrics to the agent namespace,agent.googleapis.com, you must install the collector on the host system of thetechnology being monitored. If the collector is not installed on the hostsystem, metrics are still sent to Monitoring, but to a separate,external namespace,external.googleapis.com/bluemedora/generic_node/. As aresult, existing dashboards and alerts may not function correctly since thenamespace of the underlying metrics changed.

To install the collector, complete the following steps:

1. In BindPlane, navigate toCollectors.

2. ClickAdd Collector.

3. Select your host system's operating system.

4. Click theClipboard icon to copy the installation command.

5. Log into the host system you want to install the collector on and paste andrun the command.

You can also install the collector through Google Deployment Manager. Forinstructions and security requirements on this deployment, refer to theGCPCollector Deploymentsguide.

Connecting to a data source

A source is any object you want to monitor. It could be a database, a webservice, or even a hardware device in your data center. To add a source,complete the following steps:

1. In BindPlane, navigate toSources.

2. ClickAdd Source.

3. Select which type of source you want to monitor.

4. Select the collector you installed on the host system.

5. Enter your credentials and clickTest Connection to verify that yourconnection is working correctly.

6. Optionally, you can review the metrics that are configured to be sent toMonitoring and turn off any metrics that you don't need.Turning off these metrics can help you manage costs.

7. ClickAdd to begin monitoring. To see what credentials each sourcerequires or for other information, refer to thesourcedocumentation.

Transferring existing dashboards and alerts

After installing the collector and connecting to a data source, your existingdashboards and alerts continue to work as they did previously.

If you have any issues, such as missing data, ensure the followingconditions are met:

• The collector is installed on the host system of the technology you're tryingto monitor.

• The data source is in a healthy state in BindPlane.

Managing your costs

Google has partnered with Blue Medora to bring BindPlane toMonitoring customers at no additional cost, licenses, orcontracts. However, if you ingest more monitoring data and log data through BlueMedora than you did through the Monitoring agents, you mightincur higher usage fees. For information on pricing, which applies to all custommetrics and logs over the free quota, seeGoogle Cloud Observability pricing.

To help manage your costs, BindPlane lets you to control how much data is sentto Monitoring in two ways:

• Tune your collection intervals: Collection intervals are set to 1 minuteby default. Increasing the collection interval to 2 minutes would send halfas much data to Monitoring for the given source. Increasingthe interval to 10 minutes would send one-tenth as much data. Tuning the datacollection interval lets you to find the balance between data resolution andcost that is right for your organization.

  To tune this interval, on theSources detail page, clickConfigureand then update theCollection interval field.

• Disable the collection of unneeded metrics: When a source is configured,collection is enabled for all resource types and metrics. If you don't need aspecific resource type or individual metric sent to Cloud Monitoring, thenyou can disable them to reduce the amount of data sent, reducing your costs.

  To disable unneeded metrics, on theSources detail page, clickMetrics and disable metrics collection by clicking theCollecttoggle.

Metrics guide

In addition to the metrics previously collected by the Monitoringagent, the Bindplane integration collects additional metrics, expanding thenumber of metrics collected for each technology. These additional metrics aresent to theexternal.googleapis.com/bluemedora/generic_node/ namespace.Deprecated Monitoring agent metrics that are now collected by theequivalent BindPlane integrations are sent to theagent.googleapis.comnamespace.

The following table lists the number of metrics collected by theCloud Monitoring agent and the number of additional metrics available fromBindPlane.

Integration name	Cloud Monitoring metrics	BindPlane metrics
Cassandra	7 metrics	257 metrics
Elasticsearch	18 metrics	160 metrics
HBase	23 metrics	200 metrics
Kafka	18 metrics	100 metrics
MongoDB	12 metrics	90 metrics
PostgreSQL	7 metrics	100 metrics
RabbitMQ	4 metrics	100 metrics
Tomcat	7 metrics	100 metrics
Varnish	3 metrics	170 metrics
ZooKeeper	14 metrics	30 metrics