Bindplane Hybrid Metric Collection Cost Optimization

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your enterprise operates a hybrid cloud architecture comprising Google Cloud workloads and critical on-premises database clusters (such as Cassandra and Elasticsearch). You have been tasked with centralizing infrastructure and database metrics into Google Cloud Monitoring without modifying underlying application code.

After deploying BindPlane to collect telemetry from your on-premises servers, you observe that the volume of ingested metric data in Cloud Monitoring is exceeding budget thresholds. Your monitoring policy only requires performance metrics at a 5-minute granularity for standard operational dashboards, and several default component metrics are unnecessary for your operational alerting.

What should you do to optimize your hybrid metric pipeline and reduce ingestion costs?

Re-architect the monitoring pipeline to instrument all on-premises databases with OpenCensus exporters sending time series directly to the Cloud Monitoring API.

Deploy Google SecOps collection agents alongside BindPlane to parse SYSLOG feeds into Unified Data Model (UDM) events and suppress low-priority metrics.

Configure Cloud Logging sinks on Google Cloud to export incoming BindPlane data into BigQuery and schedule 5-minute aggregation queries.

Navigate to the Sources detail page in BindPlane, increase the collection interval from 1 minute to 5 minutes, and toggle off unneeded resource types and individual metrics.

Professional Cloud DevOps Engineer

Bindplane Hybrid Metric Collection Cost Optimization

Related questions