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.

The OpenTelemetry Collector plays many different roles in the observability ecosystem. One of its most important roles is that of a telemetry processor. Recent upgrades to the Collector have enhanced its ability to condense, derive, replicate, and reason about telemetry streams. This is achieved with a new class of pipeline components called Connectors.