Operations | Monitoring | ITSM | DevOps | Cloud

Back in March, we introduced the Grafana Cloud Agent, a subset of Prometheus built for hosted metrics. It uses a lot of the same battle-tested code as Prometheus and can save 40 percent on memory usage. Ever since the launch, we’ve been adding features to the Agent. Now, there’s a clustering mechanism, additional Prometheus exporters, and support for Loki. Our latest feature: Grafana Tempo! It’s an easy-to-operate, high-scale, and cost-effective distributed tracing system.

Implementing distributed tracing is fast becoming a fundamental expectation when building modern (distributed) systems. However, this is yet another thing for developers to learn, and configuring distributed tracing on Kubernetes is hard, right? Actually, no. Getting started with Jaeger on Kubernetes has never been easier.

Yesterday we were excited to announce Logz.io Distributed Tracing, the most recent addition to our Cloud-Native Observability Platform. This is such a special launch for us because it makes Logz.io the only place where engineers can use the best open source monitoring tools for logs, metrics, and traces – known as the ‘three pillars’ to observability – together in one place.

Today was a monumental day for Logz.io and our entire community. There is nothing more inspiring than seeing how people use the technology we’ve built to enhance their businesses. At ScaleUP 2020, our first ever global user conference, we hosted an exciting day of technical, customer-led sessions with our community. We also had the privilege of unveiling some ground-breaking new solutions and enhancements to our end-to-end cloud-native observability platform.

Grafana Tempo, the recently announced distributed tracing backend, relies on integrations with other data sources for trace discovery. Tempo’s job is to store massive numbers of traces, place them in object storage, and retrieve them by id. Logs and exemplars allow users to quickly and more powerfully jump directly to traces than ever before. Let’s dig into some examples with a live playground to try it out!

These days, the internal workings of Linux applications involve many different moving parts. Sometimes, it can be rather difficult to debug them when things go wrong or run slower than expected. Tracing an application’s execution is one way of understanding potential issues without diving into the source code. To this end, we wrote an app-tracing tool called etrace, designed to detect performance bottlenecks and runtime issues in snaps.

Today is the last day of ObservabilityCON 2020! We hope you’ve had the chance to catch the talks so far, and will tune in live for today’s sessions. View the full schedule on the event page, and for additional information on viewing, participate in Q&As, and more, check out our quick guide to getting the most out of ObservabilityCON. If you aren’t up-to-date on the presentations so far, here’s a recap of day three of the conference.

Grafana Labs is proud to announce an easy-to-operate, high-scale, and cost-effective distributed tracing system: Tempo. Tempo is designed to be a robust trace id lookup store whose only dependency is object storage (GCS/S3). Join us in the Grafana Slack #tempo channel or the tempo-users google group to get involved today!

Datadog has a long-standing commitment to open standards. Our integrations with OpenMetrics, JMX, and WMI, as well as our implementation of the tried-and-true StatsD protocol, enable you to collect data with the tools and libraries that fit best into your workflows.

AWS is announcing the AWS Distro for OpenTelemetry today. This is a distribution of OpenTelemetry, itself a CNCF sandbox project. This is part of a wider push towards Open Source, cloud native technologies, and modern observability, all based on Open Standards. This push can be observed across the whole technology sector, but with increasing velocity from within AWS. As they are the largest public cloud provider by far, this is noteworthy in and of itself.