Skip to main content
Ent+
This feature is available as an add-on for the Honeycomb Enterprise plan. Please contact your Honeycomb account team for details.

​
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

Honeycomb Docs - Rename Field - image 1

​
Standalone Processor

apiVersion: bindplane.observiq.com/v1
kind: Processor
metadata:
  id: rename_fields_v2
  name: rename_fields_v2
spec:
  type: rename_fields_v2
  parameters:
    - name: telemetry_types
      value: ['Logs']
    - name: condition
      value: 'true'
    - name: fields
      value:
        - fieldType: body
          key: status
          value: status_code