Trainers

Martin LEKPA

Martin LEKPA

Tech Lead et formateur Observabilité





Chapters | Training

1. Introduction and Architecture

2. Syntax and Configuration (Alloy Language)

3. Metrics Collection (Prometheus & Ecosystem)

5. Traces (Tempo)

Ingestion and transformation of traces.


Traces

Transformation

6. Continuous Profiling (Pyroscope)

Setting up profile collection.


Continuous Profiling

7. Cluster Mode

High availability and load balancing.


Clustering Mode

8. Advanced Deployment

Deployment on Kubernetes.


Alloy on Kubernetes

Cas concrets & Applications

Unified Telemetry Collection

Replace multiple agents with a single Alloy binary for centralized collection of logs, metrics, and traces.

OTLP Data Transformation

Receive, filter, modify, and route OpenTelemetry data to various observability databases.

Kubernetes Dynamic Discovery

Automatically discover and scrape pods and services dynamically deployed in a Kubernetes cluster.

Continuous Profiling

Collect application performance profiles (via Pyroscope) continuously to quickly identify bottlenecks.

Questions Fréquentes (FAQ)

It is an open-source, vendor-neutral telemetry collector designed to replace Grafana Agent. It is OpenTelemetry (OTel) compatible.
Yes, Alloy combines the features of Promtail and Grafana Agent and includes native support for OpenTelemetry.
Alloy uses a declarative syntax based on River (similar to Terraform's HCL) which simplifies pipeline creation.
Absolutely, Alloy offers full native support for receiving, processing, and exporting data (Traces, Logs, Metrics) via the OTLP protocol.
grafana alloy trainingalloy opentelemetry tutorialgrafana alloy course englishreplace grafana agent with alloygrafana alloy observability pipelinealloy metrics logs traces collectiongrafana alloy clusteringalloy clusteringalloy live debugginggrafana alloy uialloy lokiloki processalloy configurationalloy configalloy portalloy journaldalloy prometheusalloy riverprometheus.exporter.self