Bindplane

OTel Unplugged 2026: quick recap from Adnan Rahić 👇 Community-led sessions. Zero sales pitches. Lots of real talk. The conversations centered on the things teams are actually dealing with right now: managing collectors at scale, taming fast-growing telemetry pipelines, and where OpenTelemetry needs to evolve next to keep up. This is the kind of forum where the roadmap gets shaped. If you’re building with OpenTelemetry, this is the energy that matters. Watch here: https://lnkd.in/eBsCf9my #OpenTelemetry #Observability #TelemetryPipelines #SIEM #CloudNative

Migrating your observability stack is hard. Doing it across a fleet of OpenTelemetry Collectors shouldn't make it harder. With Bindplane, one config change rolls out to your entire fleet. The overall arc is straightforward: start with parallel ingestion, shift services one at a time as your team validates each one in ClickStack, and eventually decommission the legacy destination. https://lnkd.in/gCi9XzEH

🚨 Claude Code + OpenTelemetry = Per-Session Cost Visibility Your AI coding assistant is already emitting telemetry. The real question is… are you collecting it? Claude Code exports OpenTelemetry signals out of the box, including per-session cost in USD, token usage (input/output/cache), session counts, lines of code changed, API requests, and tool calls. Most teams only see aggregate spend in the Anthropic console. No per-developer breakdown. No per-workflow insight. No visibility into which prompts or tool calls are driving token burn. That changes now. In a new guide, Adnan Rahić walks through how to route Claude Code telemetry into Bindplane in about five minutes with no custom instrumentation required. Just enable OTLP export, point it to a collector, and you’ve got cost, token, and session visibility flowing into the same pipeline as the rest of your telemetry. Even better: you can redact sensitive tool parameters before data leaves your environment. AI tooling is becoming part of your production workflow. It deserves the same observability discipline as everything else. 👉 Read the guide and start tracking Claude Code the right way: https://lnkd.in/gnTgBn3j #OpenTelemetry #DevOps #PlatformEngineering #AIObservability #TelemetryPipeline

ClickHouse was built for high ingestion and high cardinality. Now you can feed it clean logs just as easy. In this quick walkthrough, Chelsea Wright shows how Bindplane connects to ClickHouse using a ready-to-go blueprint. Logs are parsed, deduped, batched, and normalized before they land downstream. At the same time, you’re managing collectors at scale. Control thousands of OpenTelemetry Collector instances from a single visual control plane. Roll out changes safely. Eliminate config drift. Clean telemetry. High-volume ingestion. Centralized control. 🎥 Watch the full walkthrough https://lnkd.in/eWbwqGzj #ClickHouse #ClickStack #OpenTelemetry #TelemetryPipeline #Observability

🚀Announcing: Bindplane + VictoriaMetrics We’ve added native destinations for the VictoriaMetrics ecosystem, making it easier than ever to route OpenTelemetry metrics, traces, and logs at scale. VictoriaMetrics is built for high-throughput, cost-efficient storage. Bindplane is built to control and optimize the collectors feeding it. Together, that means: ✅Fewer manual exporter configs. No collector drift. No guesswork. ✅Upstream filtering, sampling, masking, and enrichment before ingestion ✅Native destinations for VictoriaMetrics, VictoriaTraces, and VictoriaLogs ✅Centralized control over thousands (or millions) of OpenTelemetry Collectors VictoriaMetrics scales ingestion. Bindplane controls what gets ingested. As telemetry volumes grow, complexity shifts upstream. This integration gives teams a single control plane to manage how data flows into VictoriaMetrics across cloud, hybrid, and on-prem environments. If you’re running VictoriaMetrics and want tighter control over cost, consistency, and rollout safety, you can try the integration now. 👉 https://lnkd.in/ehgB7AjS #OpenTelemetry #Observability #TelemetryPipeline #CloudNative

There’s a simple way to cut observability and SIEM costs without sacrificing visibility: Don’t send everything to your expensive tools. Pipeline Playbook: - Rehydrate on demand when you actually need it - Reduce and filter what goes to your primary destination (SIEM/APM) - Route full fidelity telemetry to low cost storage (GCS/S3) for compliance + investigations It’s one pipeline with multiple outcomes and it’s one of the fastest ways to keep telemetry growth from turning into an unplanned budget line. #OpenTelemetry #ObservabilityEngineering #SecOps #TelemetryPipeline

🚨 Through 2026, AI will automate 80% of telemetry pipeline work. What does that actually mean for DevOps and Security teams? In a new piece for CPO Magazine, Ryan Goins breaks down how AI-native automation is changing telemetry pipelines from weeks of hand-built OpenTelemetry configs to AI-generated pipelines reviewed in hours. The big shift is in the elevation. As OpenTelemetry standardizes and AI learns from thousands of real-world deployments, teams stop reinventing the same pipelines and start focusing on what actually matters: • compliance • cost control • security coverage • business-critical signals Instead of writing YAML and debugging exporters, DevOps and SecEng teams become reviewers, strategists, and decision-makers, defining intent while AI handles the repetitive 80%. If you care about observability scale, telemetry costs, or where DevOps roles are headed next, this one’s worth a read. 👉 https://lnkd.in/eQg8A3-K #OpenTelemetry #DevOps #Observability #SecurityEngineering #AIinDevOps #Telemetry #PlatformEngineering

Ever wonder what your telemetry pipelines are actually doing? In this quick walkthrough, our team gives a high-level tour of Bindplane, how collectors are organized, how data flows through gateways, and how teams use pipeline intelligence to reduce noise, control costs, and safely roll out changes at scale. If you’re running OpenTelemetry (or thinking about it), this is a great place to start. ▶️ https://lnkd.in/eX-Gi6aS #OpenTelemetry #Observability #TelemetryPipelines #Bindplane #DevOps #SRE

NGINX might power your infrastructure, but it can also quietly overwhelm your Elasticsearch cluster. We just released new Bindplane Blueprints for Elasticsearch that turn raw NGINX access and error logs into clean, structured, ECS-aligned data before they ever hit your cluster. That means: Sensitive data masked at the edge Faster bulk indexing and leaner storage Less noise from health checks and static assets Instant compatibility with Kibana’s native dashboards Built-in sampling and deduplication to prevent log storms In real-world scenarios, teams are seeing up to 77% reduction in log volume out of the box. Resulting in lower ingestion costs, faster Kibana dashboards, and production-ready NGINX pipelines you can deploy in minutes. If you’re running Elasticsearch at scale, check it out: https://lnkd.in/e9Sgi6rK #Elasticsearch #Kibana #OpenTelemetry #NGINX #ObservabilityEngineering #TelemetryPipeline

Blueprint of the month: Windows Events → Google SecOps ✅ If you're onboarding endpoints into Google SecOps, Windows Event logs are one of the first places teams start - and one of the easiest places to get stuck. This blueprint gives you a clean, production-ready starting point: - SecOps destination configured for GRPC - Standardization + batching processors pre-wired - Windows Events source (sent as raw logs so SecOps can parse correctly) - Namespace + key/value labels so you can search immediately inside SecOps Drop it in, roll it out and ship logs confidently. #GoogleSecOps #WindowsEvents #OpenTelemetry #SecOps