Operations | Monitoring | ITSM | DevOps | Cloud

We’ve all been surprised by our cloud monitoring bill at one time or another. If you are a BindPlane OP customer ingesting Host Metrics into Google Cloud Monitoring, you may be wondering which metrics are impacting your bill the most. You may have metrics enabled that aren’t crucial to your business, driving unnecessary costs. How do we verify that and remediate?

If you’re a systems engineer, SRE, or just someone with a love for tech buzzwords, you’ve likely heard about “data lakes”. Before we dive deep into this concept, let’s debunk the illusion: there aren’t any floaties or actual lakes involved! Instead, imagine a vast reservoir where you store loads and loads of raw data in its natural format. Now, pair this with the idea of observability and telemetry pipelines, and we have ourselves an engaging topic.

Often it can be a challenge to collect data into a monitoring environment that does not natively support that data source. Bindplane can help solve this problem. As the Bindplane Agent is based on OpenTelemetry (and is also as freeform as possible), one can bring in data from disparate sources that are not easily supported by the Splunk Universal Forwarder.

Much of the log data we handle doesn’t offer substantial insight and can be conveniently removed from your logs, helping us reduce costs. What may seem like a small adjustment, like deleting an attribute, can have significant implications when scaled up. A typical case involves fields in your logs presenting empty values or housing data considered irrelevant. Below we’ll take a look at a few examples of what this looks like and how you can take action in BindPlane OP.

As the foundation of your observability stack, BindPlane OP provides great visibility into your telemetry data, all the way from collection to its final destination. With the introduction of Live Preview in BPOP Enterprise, and a brand new processor workflow, we’ve now made this even better.

You may be thinking, “What on earth is an observability pipeline? And how does the Super Mario World fit in?” Hold on to your hat, my friend, because you’re about to find out!

Splunk is a popular logging, and in the case of Splunk Cloud also metrics, platform. The BindPlane Agent is capable of integrating with Splunk; both for incoming telemetry to a Splunk Indexer and outgoing telemetry from a Splunk Forwarder. By integrating in this manner, telemetry not natively supported by Splunk can be sent in; and going the other way the telemetry can be sent to other platforms.

Managing configuration changes within BindPlane OP is a straightforward process when using the newly introduced Rollouts features to deploy your changes. Rollouts provides a user-friendly platform for tweaking configurations, staging modifications, and implementing them across your agent fleet only when you’re satisfied with the changes.

Adding additional attributes to your telemetry not only provides valuable context to your observability pipeline but also enhances the flexibility and precision of your data operations. Consider, for example, the need to route data from specific geographical locations, like the EU, to a designated destination. With a ‘Location’ attribute added to your logs, you can seamlessly achieve this.

When engaging with potential customers, we are often asked “how can we reduce spend on our observability platform like Splunk or Data Dog and simultaneously justify the cost of BindPlane OP?” Let’s dive in and see how the powerful capabilities of BindPlane OP can reduce your total ingest, and get a positive ROI on your BindPlane OP investment.