Going Beyond the Three Pillars of Observability

The three pillars of observability have proven themselves a crucial way to trend, tune, and troubleshoot systems large and small. These are critical day-to-day operations in millions of organizations, as attested by years of collective infrastructure management experience. But as globally-distributed infrastructures become more common, are they enough? Just to make sure we are all on the same page, the three pillars are: logging, metrics, and tracing.


AWS Distro for OpenTelemetry will send metrics and traces to Datadog

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 Distro for OpenTelemetry, Grafana, Prometheus, Loki, OpenMetrics, and beyond: How Open Standards continue to shape modern observability

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.


Lightstep Makes Kubernetes Observability Seamless With OpenTelemetry and Ambassador

The goal of OpenTelemetry, ultimately, is to make observability a seamless and built-in feature of cloud-native software. However, there’s more to this than simply integrating with frameworks like gRPC or Spring Boot - observability works best when you combine data from a variety of sources. The OpenTelemetry Collector is an integral part of this, acting as a “swiss-army knife” that can integrate metrics, logs, and traces from a variety of sources and translate them as needed.


Tracing without Limits: live-query all traces, retain only the ones you need

Tracing is a critical part of monitoring application performance, especially as organizations shift to deploying services using distributed systems, serverless computing, and containerized environments. Teams need real-time, end-to-end visibility into all of the traces relevant to performance issues such as an application outage or an unresponsive service, but managing tracing costs often results in gaps in valuable tracing data.


Announcing Native OpenTelemetry Support in Splunk APM

At Splunk, we've been leading the way in observability and helping accelerate the adoption of the OpenTelemetry project. With the trace specification reaching a stable maturity level and several SignalFx Gateway and client library capabilities being upstreamed, we're ready to go all-in while we continue accelerating the growth and adoption of OpenTelemetry beyond the commitments we made last year.

Jaeger Essentials: Distributed Tracing from Dapper to Jaeger

If you are dealing with microservices, serverless architecture, on any other type of distributed architecture, you have probably heard the term “Distributed Tracing.” You may have been wondering what it’s all about, and where should you start, in this post, I’ll tell you about the journey we passed at Duda, from the day we heard about distributed tracing and started to explore whether it will be useful to use it in our company, to the exploration on what is distributed tracing a