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 processors.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
service.namespace: Your application name.
service.name: Your application's tier name.

For more information, see Attribute Descriptions.

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. 
    - key: service.namespace
      action: upsert
      value: my-shop
    - key: service.name
      action: upsert
      value: checkout-service

Note:

Alternatively, you can configure resource attributes in any of the following ways:

To configure resource attributes from your application code, set the service.name and service.namespace. See Instrument Applications with Splunk AppDynamics for OpenTelemetry
Set service.name and service.namespace in the OTEL_RESOURCE_ATTRIBUTES environment variable. See Instrument Applications with Splunk AppDynamics for OpenTelemetry .

Batch Processor

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

Configure the following processors.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