Exciting news: it’s now possible to build a custom distribution of the OpenTelemetry Collector and remotely manage it with BindPlane. Though not all of BindPlane’s capabilities are available when managing a custom distribution (yet), it’s #prettycool, as it cracks open the door for teams looking to BYOF (bring your fleet), and manage them with our OTel-native telemetry pipeline.

Keeping smooth and safe operations now relies entirely on observability. But as there's more and more data to keep track of, the costs are going up. This makes it hard for your companies to balance how well things are running and their budgets. OpenTelemetry can help by making a standard way to collect and process all the data. We're going to share how OpenTelemetry can save you money on observability and why having too much data can be costly.

Trace spans are captured in the runtime after decrypting the request. This means that any sensitive data is available in plain text. This is also the case for logging; however, logging requires an explicit log statement to be coded by the engineer. Additionally, engineers can add arbitrary information to trace spans, which could expose sensitive information. Collecting sensitive information in trace spans or logging events could expose an organization to a number of risks.

Last time we spoke, I told you about our (then) brand-spankin’-new OTel over HTTP implementation, in both our OpenTelemetry Source and Destination. That was a little over a year ago, also known as a lifetime in tech! I wanted to take another opportunity to speak to you and introduce some of our new OpenTelemetry features, and share how you can put them into practice!

We cover everything from initial setup to practical tips for monitoring and improving your fasthttp applications. Follow along to enhance your observability and get a clearer view of your app’s performance.

OpenTelemetry can be used to trace React applications for performance issues and bugs. You can trace user requests from your frontend web application to your downstream services. OpenTelemetry is an open-source project under the Cloud Native Computing Foundation (CNCF) that aims to standardize the generation and collection of telemetry data. Using OpenTelemetry Web libraries, you can instrument your React apps to generate tracing data.

Master log collection in Kubernetes with OpenTelemetry's filelog receiver. Learn to configure, optimize, and troubleshoot log collection from various sources including syslog and application logs. Discover advanced parser operator techniques for robust observability.

Learn to enable hot reload for the OpenTelemetry Collector to update configurations on the fly, improving your observability system's agility.

Distributed tracing is becoming a critical component of any application's performance monitoring stack. However, setting it up in-house is an arduous task, and that's why many companies prefer outside tools. Jaeger and Zipkin are two popular open-source projects used for end-to-end distributed tracing. Let us explore their key differences in this article.

It’s a bold claim for me to say that every developer can benefit from something 40% of them haven’t heard of, but hear me out. I was among the 40% who didn’t know tracing existed until this summer. Still, I spent the last three months learning why it’s critical to a developer’s workflow and the different ways developers pragmatically use it. In this blog, I hope to show you that you can benefit from tracing regardless of your stack, role, size, or project.