Rename Field
Edition: Enterprise
Description
The Rename Field processor can be used to rename resource, attribute, and log body fields.
Supported Types
Metrics | Logs | Traces |
---|---|---|
✓ | ✓ | ✓ |
Configuration Table
Parameter | Type | Default | Description |
---|---|---|---|
telemetry_types | enums | ["Metrics", "Logs", "Traces"] | The list of telemetry types the processor will act on. |
resource_keys | map | {} | A map of resource keys to rename. The value represents the new name. |
attribute_keys | map | {} | A map of attribute keys to rename. The value represents the new name. |
body_keys | map | {} | 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
Standalone Processor
apiVersion: bindplane.observiq.com/v1
kind: Processor
metadata:
id: rename_status
name: rename_status
spec:
type: rename_field
parameters:
- name: telemetry_types
value: ["Logs"]
- name: body_keys
value:
status: "status_code"
Updated 3 months ago