Type to search.

Some fields show as empty in Discover

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.

A field that you add to the Discover table can show empty cells even though your data has values for it. For other common issues, refer to the blog post Learn how to resolve common issues with Discover.

  • The cells of a field that you added as a column in the results table are empty for some or all results.
  • You expect values for that field.

This can happen in several cases:

  • With runtime fields and regular keyword fields, when the string exceeds the value set for the ignore_above setting used when indexing the data into Elasticsearch.
  • Due to the structure of nested fields, a leaf field added to the table as a column doesn't contain values in any of its cells.

If the field is a nested field:

  1. Open the fields list in the sidebar and find the root field of the nested field.
  2. Add the root field as a column. The table shows a JSON representation of the values of the nested field.

To learn more about how Discover reads nested fields, refer to the blog post about how Discover uses the Fields API.

If the field is a keyword field with long strings, check the ignore_above setting in the mapping reference.