Operations | Monitoring | ITSM | DevOps | Cloud

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.

Winter has fully set in at Bindplane’s Michigan-based headquarters, but we’re keeping warm with the excitement from this piping-hot announcement and accompanying release. It’s just the thing to ignite the hearts, minds, and typing fingers (?) of our team and observability professionals as we kick off 2025.

Maintaining and visualizing telemetry data efficiently is super important for DevOps and SecOps teams. OpenTelemetry, a fantastic open-source observability framework, can really help with this without being too costly. Picture having a simple process that improves your data and helps your team make smart decisions without spending too much money. Let's chat about some budget-friendly ways to set up OpenTelemetry agents.

OpenTelemetry has quickly become a must-have tool in the DevOps toolkit. It helps us understand how our applications are performing and how our systems are behaving. As more and more organizations move to cloud-native architectures and microservices, it's super important to have great monitoring and tracing in place. OpenTelemetry provides a strong and flexible framework for capturing data that helps DevOps engineers keep our systems running smoothly and efficiently.

OpenTelemetry has quickly become a must-have tool in the DevOps toolkit. It helps us understand how our applications are performing and how our systems are behaving. As more and more organizations move to cloud-native architectures and microservices, it's super important to have great monitoring and tracing in place. OpenTelemetry provides a strong and flexible framework for capturing data that helps DevOps engineers keep our systems running smoothly and efficiently.

Solving system failures and performance issues can be like solving a tough puzzle for engineers. But trace data can make it simpler. It helps engineers see how systems behave, find problems, and understand what's causing them. So let’s chat about why trace data is important, how it's used for finding the root cause of issues, and how it can help engineers troubleshoot more effectively.