Configure Processors

Processors allow additional processing of data, such as data enrichment and batching.

You must configure the processors:

Resource Processor

Add the Controller account, host, and port to the resource processor:

In the resource: attributes: section, add the following:

  • appdynamics.controller.account: Your Splunk AppDynamics Controller account name
  • appdynamics.controller.host: Your Splunk AppDynamics Controller hostname
  • appdynamics.controller.port: Your Splunk AppDynamics Controller port number
Warning: You also must add service.name and service.namespace resource attributes, but you have three options for how to add them:
  • Set the service.name and service.namespace from inside your application code.
  • Set service.name in your OpenTelemetry otel-config.yaml file.
  • Set service.name and service.namespace in the OTEL_RESOURCE_ATTRIBUTES environment variable.

See Configure Resource Attributes for more information.

processors:
  resource:
    attributes:
  	- key: appdynamics.controller.account
      action: upsert
      value: "acme"
  	- key: appdynamics.controller.host
      action: upsert
      value: "acme.saas.appdynamics.com"
  	- key: appdynamics.controller.port
      action: upsert
      value: 443 # can be an integer or string.

Batch Processor

The batch processor accepts spans, metrics, or logs and places them into batches in the OpenTelemetry Collector pipeline.

Configure the following batch: attributes to help improve performance:

  • timeout: Time after which a batch is sent, regardless of size. The default is 30 seconds.
  • send_batch_size: Number of spans or metrics after which a batch is sent. The default is 8,192.
    Note: We recommend batching 90 spans or less per request for optimal results.
processors:
  batch:
    timeout: 30s
    send_batch_size: 90