This option is for advanced users who are familiar with the OpenTelemetry Collector, it’s configuration, and with Kubernetes CRDs.

You can browse the full list of processors that Odigos includes here.

To view the configuration for each processor, it is recommended to visit the README of this component in OpenTelemetry Collector Contrib codebase.

Adding a processor to your Odigos pipeline can be done by creating a Processor custom resource in your Kuberenetes cluster under the odigos-system namespace:

​
Configuration Options

​
Basic Example

The following example demonstrates how to add a resource attribute deployment.environment with the value production to all spans in the cluster.

1

Create a YAML file with the following content:

example-processor.yaml
apiVersion: odigos.io/v1alpha1
kind: Processor
metadata:
  name: example-processor
  namespace: odigos-system
spec:
  type: resource
  processorConfig:
    attributes:
      - key: deployment.environment
        value: production
        action: insert
  signals:
    - TRACES
  collectorRoles:
    - CLUSTER_GATEWAY
2

Apply the action to the cluster:

kubectl apply -f example-processor.yaml

This option is for advanced users who are familiar with the OpenTelemetry Collector, it’s configuration, and with Kubernetes CRDs.

You can browse the full list of processors that Odigos includes here.

To view the configuration for each processor, it is recommended to visit the README of this component in OpenTelemetry Collector Contrib codebase.

Adding a processor to your Odigos pipeline can be done by creating a Processor custom resource in your Kuberenetes cluster under the odigos-system namespace:

​
Configuration Options

​
Basic Example

The following example demonstrates how to add a resource attribute deployment.environment with the value production to all spans in the cluster.

1

Create a YAML file with the following content:

example-processor.yaml
apiVersion: odigos.io/v1alpha1
kind: Processor
metadata:
  name: example-processor
  namespace: odigos-system
spec:
  type: resource
  processorConfig:
    attributes:
      - key: deployment.environment
        value: production
        action: insert
  signals:
    - TRACES
  collectorRoles:
    - CLUSTER_GATEWAY
2

Apply the action to the cluster:

kubectl apply -f example-processor.yaml