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

Rename Field

Description

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

warning

This processor has been deprecated and replaced with a new Rename Fields processor that supports additional functionality and improved layout. While it will continue to function, it will no longer receive any enhancements and you should migrate to the new processor. For more information about the new processor, see here.

Supported Types

MetricsLogsTraces

Configuration Table

ParameterTypeDefaultDescription
telemetry_typestelemetrySelector["Logs", "Metrics", "Traces"]Choose Telemetry Type.
resource_keysmap{}A map of resource keys to rename. The value represents the new name.
attribute_keysmap{}A map of attribute keys to rename. The value represents the new name.
body_keysmap{}A map of body keys to rename. The value represents the new name.

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 Field - image 1

Standalone Processor

yaml
1apiVersion: bindplane.observiq.com/v1
2kind: Processor
3metadata:
4  id: rename_status
5  name: rename_status
6spec:
7  type: rename_field
8  parameters:
9    - name: telemetry_types
10      value: ["Logs"]
11    - name: body_keys
12      value:
13      	status: "status_code"