This option is for advanced users who are familiar with the OpenTelemetry Collector, it’s configuration, and with Kubernetes CRDs.
Processor
custom resource in your Kuberenetes cluster under the odigos-system
namespace:
Configuration Options
processorName
processorName
processorName
string
: Allows you to attach a meaningful name to the processor for convenience.- This field is optional
notes
notes
notes
string
: Allows you to attach notes regarding the processor for convenience.- This field is optional
disabled
disabled
disabled
boolean
: Allows you to temporarily disable the processor, but keep it saved for future use.- This field is optional, and defaults to
false
signals *
signals *
signals
string[]
: An array with the signals that the processor will act on.- This field is required
- Supported values:
TRACES
,METRICS
,LOGS
collectorRoles *
collectorRoles *
collectorRoles
string[]
: An array with the collector roles that the processor will act on.- This field is required
- Supported values:
CLUSTER_GATEWAY
,NODE_COLLECTOR
type *
type *
type
string
: The type of the processor.- This field is required
- The name of the processor you want to use, as defined in the OpenTelemetry Collector (batch, attributes, etc).
orderHint
orderHint
orderHint
number
: If your processors need to run in a specific order relatively to other processors, you can hint the order by setting an integer value here.- This field is optional
- The lower the value, the earlier the processor will run in the collector pipeline. If the value is missing or 0, the processor will run in an arbitrary order in the collector pipeline.
processorConfig
processorConfig
processorConfig
object
: A field to pass configuration to the processor.- This field is optional
- The structure of this field is specific to each processor, and you can find the configuration options for each processor in the [OpenTelemetry Collector Contrib codebase](
Basic Example
The following example demonstrates how to add a resource attributedeployment.environment
with the value production
to all spans in the cluster.
1
Create a YAML file with the following content:
example-processor.yaml
2
Apply the action to the cluster: