Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.odigos.io/llms.txt

Use this file to discover all available pages before exploring further.

​
What are Processors?

Under the hood, Odigos uses the OpenTelemetry Collector Processors to implement actions. Processors are a class of OpenTelemetry Collector component. They are used to transform, filter, or enrich your OpenTelemetry data before it is sent to your destinations.

​
Benefits

  • Odigos Actions are language agnostic. They run in the OpenTelemetry collectors and can act on any data type (traces, metrics, logs) no matter the source or the programming language of your service.
  • Processing the data on the k8s node or the cluster level reduces the load on your services and allows you to apply the same processing rules to all your services and signals.
  • Applying actions in your cluster can reduce the volume of data sent to your backend, which can reduce your costs.
  • OpenTelemetry maintains a large collection of processors, which are ready to use and can be configured to your needs.
Actions are a powerful tool to help you manage your observability data and ensure that you are sending the right data to your backend.

​
Action Types

​
Attribute Actions

Attribute Actions are a way to modify the OpenTelemetry data recorded by Odigos Sources, before it is exported to your destinations.

​
Sampling Actions

Sampling Actions decide which traces are kept and which are dropped before they reach your destinations. Rules are organized into three categories, evaluated in order—Noisy Operation → Highly Relevant → Cost Reduction—so you can drop noise early, guarantee retention for important traffic, and cap everything else for cost.

​
Custom Actions

Odigos also supports adding OpenTelemetry processors with Kubernetes CRDs which you can apply manually, or through a GitOps workflow.