Live Workshop: Integrate Google SecOps with Bindplane - Join Us on January 29th at 11 AM ET!Sign Up Now

Rename Fields

Description

The Rename Fields processor can be used to rename resource, attribute, and log body fields.

Supported Types

MetricsLogsTraces

Configuration Table

ParameterTypeDefaultDescription
telemetry_typestelemetrySelector["Logs", "Metrics", "Traces"]The list of telemetry types the processor will act on.
ConditionstringtrueAn OTTL condition that must evaluate to true to apply this processor. By default, the processor applies to all telemetry.
Field TypestringattributesDetermines whether the field is renamed in the body, attributes, or resource fields of the telemetry. Note: Body fields are applicable only for logs.
Old Namestring""Specifies the existing field in the telemetry that the processor will rename.
New Namestring""Indicates the new field name that will replace the old field name in the telemetry data.

Example Configuration

Renaming log body fields

In this example, we rename the status field in a log body to status_code. Since this change only applies to logs, we have disabled metrics and traces for this processor.

Web Interface

observIQ docs - Rename Fields - image 1

Standalone Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Processor
3metadata:
4  id: rename_fields_v2
5  name: rename_fields_v2
6spec:
7  type: rename_fields_v2
8  parameters:
9    - name: telemetry_types
10      value: ['Logs']
11    - name: condition
12      value: 'true'
13    - name: fields
14      value:
15        - fieldType: body
16          key: status
17          value: status_code