Type to search.

Convert processor

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 9.3+

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

Availability

  • Generally available since 9.3

    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 Convert processor converts a field to a different data type. For example, you could convert a string to an integer.

To convert a field to a different data type:

  1. Select Create → Create processor.
  2. Select Convert from the Processor menu.
  3. Set the Source Field to the field you want to convert.
  4. (Optional) Set Target field to write the converted value to a different field.
  5. Set Type to the output data type.
Note

If you add a Convert processor inside a condition group (a WHERE block), you must set a Target field.

This functionality uses the Elasticsearch Convert processor internally, but you configure it in Streamlang. Streamlang doesn't always have 1:1 parity with the ingest processor options and behavior. Refer to Processor limitations and inconsistencies.

In YAML mode, configure the convert processor using the following parameters. For the complete Streamlang syntax, refer to the Streamlang reference.

Parameter Type Required Description
from string Yes Source field containing the value to convert.
type string Yes Target data type: integer, long, double, boolean, or string.
to string No Target field for the converted value. Defaults to the source field.
ignore_missing boolean No When true, skip this processor if the source field is missing.
Note

When using convert inside a condition (where block), you must set a to field that is different from from.

YAML
- action: convert
  from: attributes.status_code
  type: string
  to: attributes.status_code_int