The AI-Driven Security Pipeline: Bindplane at RSAC 2026 Conference
RSAC 2026 Conference is right around the corner, and we're unveiling new security capabilities at Booth N-5285. Book a 15-minute slot if you want an in-person walkthrough!
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
OpAMP for OpenTelemetry: Managing Collector Fleets and Introducing the New OpAMP Gateway Extension
Today, Bindplane is launching the OpAMP Gateway Extension in alpha — a new component that extends OpAMP fleet management into network-segmented and firewalled environments where direct agent-to-server connectivity is not possible. It also addresses fleet scaling by fanning many agent connections into a small upstream pool, reducing connection load on the OpAMP server. We also hope to donate the OpAMP Gateway Extension upstream to the OpenTelemetry project and welcome community contributions.
Bindplane Community Call in March 2026
Tune in for the Bindplane Community Call in March to learn more about SSO going GA, a wave of new updates, connectors, sources, and destinations, including a VictoriaMetrics partner integration — and a preview of what we're building next. We'll also share details on meeting the Bindplane team at KubeCon + CloudNativeCon Europe in Amsterdam. As always, hands-on demos and a live Q&A at the end.
Claude Code + OpenTelemetry: Per-Session Cost and Token Tracking
I was looking at our Claude Code spend in the Anthropic console the other day. Aggregate cost, aggregate tokens — no breakdown by developer, no breakdown by session. I knew my Hackathon team had been using it heavily on building out new features for the OpenTelemetry Distro Builder. But heavily how? I had no idea. Turns out Claude Code has been emitting OpenTelemetry signals the whole time. Per-session cost, token counts, every tool call it makes on your codebase.
Bindplane + VictoriaMetrics: Unified Telemetry for Metrics, Traces, and Logs at Scale
We’re excited to announce new native Bindplane destinations for the VictoriaMetrics ecosystem. It’s now easier to collect, process, and route OpenTelemetry metrics, traces, and logs at scale. You can directly connect VictoriaMetrics’ high-performance storage engines to Bindplane’s vendor-neutral, OpenTelemetry-native telemetry pipeline.
Bindplane Blueprints for Elasticsearch: Production-Ready NGINX Log Pipelines for Kibana
We've just released new and easy-to-use Bindplane blueprints designed specifically for Elasticsearch as a destination. These blueprints empower teams to quickly transform raw events such as those from NGINX access and error logs into clean, structured, and ECS-compliant data optimized for high-performance visualization in Kibana.
Bindplane | Blueprints for ClickHouse: Optimize Telemetry Before It Hits ClickStack
Chelsea from the Customer Success team walks through the Bindplane Blueprints for ClickHouse guide — showing how to optimize logs, metrics, and traces before they land in ClickStack. You’ll see how to: ClickHouse is powerful. But raw telemetry at scale gets expensive fast. Bindplane acts as the control plane for your OpenTelemetry infrastructure. Blueprints let you apply production-ready processing logic instantly without YAML sprawl or config drift.
Watch 10K Telemetry Events Drain Instantly #opentelemetry #observability
We loaded 10,000 messages into a persistent queue. Then watched it vanish. This is what the Pebble persistent queue storage extension looks like inside a Bindplane-managed OpenTelemetry pipeline. Resilience under pressure.
New Persistent Queue Options - Pebble Storage Extension
Bindplane now supports the Pebble storage extension for the OpenTelemetry Collector persistent queue. Faster recovery. Durable buffering. More control over telemetry under load. Own your pipeline.
What you missed at OTel Unplugged 2026 in 8 minutes!
OTel Unplugged 2026 was different by design. Held alongside FOSDEM in Brussels, this was an unconference built by the OpenTelemetry community, for the community. No sales pitches. No product demos. Just honest conversations about what’s working, what’s broken, and where OTel needs to go next. In this recap, you’ll hear short interviews and reflections from engineers, maintainers, and practitioners on.