Type to search.

Troubleshoot transforms

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.

Use the information in this section to troubleshoot common problems.

Tip

If you can't find your issue here, explore the other troubleshooting topics or contact us.

If you encounter problems with your transforms, you can gather more information from the following files and APIs:

  • Lightweight audit messages are stored in .transform-notifications-read. Search by your transform_id.
  • The get transform statistics API provides information about the transform status and failures.
  • If the transform exists as a task, you can use the task management API to gather task information. For example: GET _tasks?actions=data_frame/transforms*&detailed. Typically, the task exists when the transform is in a started or failed state.
  • Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Unavailable This functionality is not available in Elastic Cloud Serverless. The Elasticsearch logs from the node that was running the transform might also contain useful information. You can identify the node from the notification messages. Alternatively, if the task still exists, you can get that information from the get transform statistics API. For more information, refer to Elasticsearch log4j configuration.