Observability

How the Latest API Gateway Innovations Are Reshaping Operational Efficiency and Error Metrics

August, 2024

Innovations in modern API gateways are reshaping DevOps efficiency and error metrics. Find out how GitOps and comprehensive observability are changing the game.

Monitor Your Production at a Glance With Traefik 3.0 and OpenTelemetry

Nicolas Mengin

Ingress

May, 2024

We’re continuing our deep dive series on Traefik 3.0, and in this article, we focus on how to leverage OpenTelemetry in Traefik v3.

Enhancing API Observability: Traefik Hub, OpenTelemetry, and the New Era of Data-Driven API Management

Immánuel Fodor

API Management

December, 2023

Understand the importance of OpenTelemetry in API observability, how it can be used, and how Traefik Hub sets a new standard for OpenTelemetry support.

Distributed Tracing with Traefik and Jaeger on Kubernetes

Michel Loiseleur

Kubernetes

January, 2023

In the third part of this blog series, we explore the open source project Jaeger, and how to perform request tracing for applications on Kubernetes.

Log Aggregation in Kubernetes with Traefik Proxy

Michel Loiseleur

Kubernetes

January, 2023

This is the first part of our blog series on Traefik Proxy and SRE techniques that explores how Traefik's built-in logging features can help to provide visibility.

Capture Traefik Metrics for Apps on Kubernetes with Prometheus

Michel Loiseleur

Kubernetes

March, 2022

This is the second part of the blog series on using Traefik to enable SRE practices and explores how to use Prometheus and Grafana to derive insights from metrics generated by Traefik.

Observing Kubernetes Ingress Traffic using Metrics

Kevin Crawley

Kubernetes

December, 2020

Monitoring Kubernetes ingress traffic is a critical part of an effective strategy for detecting and managing potential issues in real-time.

The Importance of Distributed Tracing and Monitoring in a Microservice Architecture

Kevin Crawley

Microservices

May, 2020

How do teams diagnose latency between microservices or collate logs from dozens of loosely coupled services, while also ensuring that any logging overhead is kept to a minimum?