Skip to main content
Configuration defines where telemetry comes from (sources), where it is sent (destinations), and optional processing (actions). You can manage all of these using the VM Agent’s interactive tool or YAML files.

​
Configuration methods

You can configure the Odigos VM Agent in two ways:
  • odictl — A terminal user interface (TUI) that you use to add and manage sources, destinations, and actions interactively.
  • YAML — Each configuration task (sources, destinations, actions) can be done via YAML; the pages linked below include a YAML tab with examples.

​
Configuration tasks

Add sources

Instrument systemd services, Linux processes, or Docker containers so the VM Agent collects their telemetry.

Add destinations

Define where telemetry is sent (for example, OTLP endpoints or supported backends). Destinations with the LOGS signal turn on application log export automatically.

Add actions

Transform, filter, or enrich telemetry before it is sent to destinations.

Instrumentation rules

Control how telemetry is recorded from your sources (attributes, headers, payloads and custom instrumentation rules).

Continuous profiling

Enable eBPF CPU profiling on the collector and export OTLP Profiles to Pyroscope.

Connect to Odigos Central

Connect this VM Agent host to Central for centralized visibility and management.
Add a destination first, then sources, then actions and instrumentation rules as needed.

​
Log collection

When a destination is configured with the LOGS signal, the VM Agent automatically collects application logs from instrumented sources and exports them. How logs are collected depends on the source kind:
The odictl Logs panel shows live logs for the odigos-vmagent and odigos-otelcol services themselves. That is separate from application OpenTelemetry logs exported to your destination.
For definitions of sources, destinations, and actions, see Key concepts in the VM Agent overview.