Implementing Distributed Tracing with Istio and Envoy

In the past few years, several organizations made the jump from monoliths to microservices architecture. This architectural pattern breaks down a large complex application into a collection of smaller loosely coupled services that are easy to maintain, scale, and deploy independently. However, the downside of modern microservices architecture is the inherent complexity of service-to-service discovery and communications.


How to get started quickly with metrics, logs, and traces using Grafana Cloud integrations

Grafana Cloud is the easiest way to get started observing metrics, logs, traces, and dashboards. When we say “easiest,” we mean it: Grafana Cloud is designed so that even novice observability users can use it. As a new user, you are not required to dive into the complexity of setting up Prometheus and figuring out how to create Grafana dashboards from scratch. Integrations are the reason why.


Embracing Open Source data collection

Open source has come a long way. One of my favorite reports on the subject is Red Hat’s State of Enterprise Open Source. For 2020, 95% of respondents said that open source is strategically important to their business needs. Here, I will be recapping my recent Illuminate presentation about embracing open source data collection and I thought it’s important to first talk about how open source has changed.


The new Grafana Cloud: the only composable observability stack for metrics, logs, and traces, now with free and paid plans to suit every use case

Oftentimes users of open source are told to go download it and figure it out… or pay for a managed solution in the cloud. So the typical choice is free and do-it-yourself or expensive and easy. With our new changes to Grafana Cloud, we are making it both free and easy to have a real, composable observability solution.


How We Improved Epsagon's Trace Search Using Epsagon

Dogfooding, aka “eating your own dog food”, is a common practice of organizations using their own products for real-world scenarios. Organizations that do it right enjoy the advantages of early-stage use-case validation, bug hunting, and feedback. Developers who actively use their own product gain confidence and a deeper understanding of their clients. Dogfooding is something we at the Epsagon team pride ourselves on.


A Recap of the KubeCon + CloudNativeCon Observability Track

OpenTelemetry has evolved so much since the 2019 KubeCon North America in San Diego, where I live-demoed OpenTelemetry on the keynote stage and highlighted our alpha to the world. We’re excited to be entering general availability of our Collector and Tracing SDKs soon. While I missed the energy from the packed crowd of over 10,000 technologists cheering me on, it was wonderful that this year’s event was more accessible than ever to a worldwide audience.


Why should OpenTelemetry be your standard for telemetry?

OpenTelemetry is a great way to combine different types of telemetry from across your application and to do so in a way that protects your organization from future vendor changes. But maybe you think your team can do better? Why not set your team out to build a new abstraction for extracting telemetry that is customized to your application and the needs of your organization? After all, your platform team will need to invest in some abstraction, why not invest in one that precisely fits your needs?


Lightstep partners with AWS on the AWS Distro for OpenTelemetry

As a cofounder of OpenTelemetry, I was delighted when AWS joined the project. Since then, we have worked together to make OpenTelemetry the best possible experience. We are proud to announce that we are partnering with Amazon to bring OpenTelemetry to AWS in a supported fashion. AWS Distro for OpenTelemetry provides an AWS-supported, production-ready release of the OpenTelemetry Collector for Lightstep customers who use OpenTelemetry on AWS.