Actions
Introduction
Actions are a way to modify the OpenTelemetry data recorded by Odigos Sources, before it is exported to your destinations.
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.
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 allow you to configure various types of sampling methods before exporting traces to your destinations.Scope Categories
Scope Categories
Odigos Sampling actions are divided into three main categories, each representing the action’s scope. The action scope defines the range that the sampler covers. The categories are:
- Global Actions: These actions sample all data without specificity. All traces flowing through Odigos will be sampled regardless of their source. For example, ErrorSampler.
- Service Actions: These sample actions are applied only to traces coming from a specified service.
- Endpoint Actions: These sample actions are applied to traces coming from a specific service and a specific endpoint. For example, LatencySampler.
Relation Between Sampling Actions
Relation Between Sampling Actions
When multiple sampling actions are configured, the most specific rule applies. For example:
- If two rules are configured: an Endpoint action for
Service: Frontend, Endpoint: /buywith a latency threshold of 1 second and a fallback of 50%, and a Global ErrorSampler with a fallback of 20%:- Error traces will always be sampled due to the Global ErrorSampler, regardless of any Service or Endpoint rule.
- Traces from
Frontend /buybelow 1 second latency will fall under the Endpoint action’s fallback and retain 50% of these traces. - Traces from
Frontend /buyabove 1 second latency will always be retained. - Any other non-error traces that are not from
Frontend /buywill be sampled at 20%.