Operations | Monitoring | ITSM | DevOps | Cloud

We’ve noticed a lot of our customers spend countless hours building and configuring processors. Either parsing JSON, standardizing log formats, normalizing timestamps, masking PII, de-duplicating logs, the list never ends. Most work revolves around recreating the same processor bundles in multiple processor nodes. Bindplane’s new Blueprints solves that boring, repetitive work by providing pre-built processor bundles you can drop into any pipeline with a single click.

Join the live stream at 11 am ET, here. Platform teams tend to start with just one, or in some cases a handful of OpenTelemetry (OTel) Collectors usually running in gateway mode. They then embrace the benefit of a vendor-neutral, standardized, telemetry collector for unified logs, metrics, and traces.

Join the live stream at 11 am ET, here. OpenTelemetry’s super-power has always been: Choice. Yet, most observability vendors still insist you run their collector. Today we’re removing that last point of friction. With Bring Your Own Collector (BYOC), Bindplane now accepts any upstream-compatible build, recognizes exactly which receivers, processors, and exporters it contains, and adapts the UI and configuration workflow on the fly.

Today, we're expanding on the integrations front, and launching new integrations for Windows events, network telemetry, and cloud storage. Here's a quick tour of what's new and why it matters.

Windows event logs can provide valuable insight into day-to-day operations and potential security issues. But making sense of that data—and getting it to the right place without overloading your systems or driving up costs—takes some planning. Bindplane helps with this by providing a flexible way to collect, process, and route Windows events. It’s designed to support security and compliance needs without adding unnecessary complexity.

Almost two years ago I wrote the first installment of what was supposed to be a 3 part series on Serverless Monitoring. Parts two and three never materialized. Today, however, I am revisiting that original idea and expanding upon it. I hope to succeed this time in making it a full three-part series. For this first installment (Revisited), I will again work with Google Cloud Run to monitor MongoDB Atlas.

OpenTelemetry is officially the second-largest project in the CNCF, only behind Kubernetes. This year we had 13.000 engineers, maintainers, and vendors show up in London.

Instead of deploying a patchwork of proprietary agents for every platform, a telemetry pipeline lets you route your data through a single, consistent layer—and send it to any backend you choose. Flexibility, achieved. But there’s a catch. If your pipeline is proprietary, you’ve only shifted the lock-in left. Sure, you can now add or swap destinations freely—but you’re still deeply dependent on a vendor in the middle of your data flow.

We're only one month into 2025, but the momentum keeps building at Bindplane. In January, we rebranded our company as Bindplane, aligning our company name with our core mission: delivering the best OpenTelemetry-native telemetry pipeline on the market. Building on that excitement, we have another announcement: we've expanded and extended our partnership with Google Cloud.

OpenTelemetry has emerged as the gold standard fueling o11y and SIEM platforms, but transitioning an existing telemetry stack requires careful planning and execution. This guide outlines a practical approach to evaluating, implementing, and scaling OpenTelemetry in production environments.