Skip to main content
Version: Next

Field Renamer


Description​

The Field Renamer processor changes the name of fields in events. It supports:

  • Single field renaming
  • Custom field names
  • Runtime name modification
  • Field name standardization

This processor is essential for:

  • Standardizing field names
  • Creating consistent naming
  • Mapping field identifiers
  • Improving readability

Required input​

The processor requires a data stream containing at least one field to rename.


Configuration​

Field​

Select the field to rename. This field's name will be changed in the output event.

New Field Name​

Enter the new name for the selected field. This name will replace the original field name in the output event.

Output​

The processor creates a new event containing:

  • All original fields from the input event
  • The selected field with its new name
  • All field values remain unchanged

Example​

Input Event​

{
"deviceId": "sensor01",
"temp": 23.5,
"humidity": 45.2,
"timestamp": 1586380104915
}

Configuration​

  • Field: temp
  • New Field Name: temperature

Output Event​

{
"deviceId": "sensor01",
"temperature": 23.5,
"humidity": 45.2,
"timestamp": 1586380104915
}

Use Cases​

  1. Data Standardization

    • Standardize field names
    • Create naming conventions
    • Map field identifiers
    • Improve consistency
  2. System Integration

    • Map field names
    • Standardize interfaces
    • Create consistency
    • Build mappings

Notes​

  • Only field names are changed
  • Field values remain unchanged
  • Original field order is preserved
  • Processing is stateless
  • Multiple renames require chaining