Type to search.

Copy fields

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

The copy_fields processor takes the value of a field and copies it to a new field.

You cannot use this processor to replace an existing field. If the target field already exists, you must drop or rename the field before using copy_fields.

This configuration:

YAML
- copy_fields:
    fields:
      - from: message
        to: event.original
    fail_on_error: false
    ignore_missing: true

Copies the original message field to event.original:

JSON
{
  "message": "my-interesting-message",
  "event": {
      "original": "my-interesting-message"
  }
}
Note

Elastic Agent processors execute before ingest pipelines, which means that your processor configurations cannot refer to fields that are created by ingest pipelines or Logstash. For more limitations, refer to What are some limitations of using processors?

Name Required Default Description
fields Yes List of from and to pairs to copy from and to. You can use the @metadata. prefix to copy values from or to event metadata.
fail_on_error No true Whether to fail if an error occurs. If true and an error occurs, any changes are reverted, and the original is returned. If false, processing continues even if an error occurs.
ignore_missing No false Whether to ignore events that lack the source field. If false, the processing of an event will fail if a field is missing.