-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Values above ignore_above mapping limit don't show up in Discover anymore #101232
Copy link
Copy link
Closed
Closed
Copy link
Labels
Feature:DiscoverDiscover ApplicationDiscover ApplicationTeam:DataDiscoveryDiscover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//Discover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//blockedbugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceimpact:highAddressing this issue will have a high level of impact on the quality/strength of our product.Addressing this issue will have a high level of impact on the quality/strength of our product.regression
Metadata
Metadata
Assignees
Labels
Feature:DiscoverDiscover ApplicationDiscover ApplicationTeam:DataDiscoveryDiscover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//Discover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//blockedbugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceimpact:highAddressing this issue will have a high level of impact on the quality/strength of our product.Addressing this issue will have a high level of impact on the quality/strength of our product.regression
Type
Fields
Give feedbackNo fields configured for issues without a type.
Kibana version: 7.13.1
Elasticsearch version: 7.13.1
Server OS version: Elastic Cloud hosted
Browser version: Firefox 89.0
Browser OS version: macOS
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
The
event.originalfield is missing in Kibana Discover for some events.Steps to reproduce:
event.original.event.original. Note that some events appear to be missingevent.original._idand query it directly from Elasticsearch and it will haveevent.original.missing-event.original.txt
Expected behavior:
event.originalwould be displayed. Or if it is being dropped for some reason, such as length, that there would be an indication that this is happening.One interesting data point is that querying for
_id:aKSBznkBdD5BTT25BM6w and event.original:*returns no results so even the KQL query seems to think thatevent.originaldoes not exist despiteaKSBznkBdD5BTT25BM6whaving anevent.original.Screenshots (if relevant):
Errors in browser console (if relevant): There are none.
Provide logs and/or server output (if relevant):
Any additional context:
I'm not sure if it has something to do with the length of the field or possibly the field's content. I saw this in cases where the event.original contained both JSON and in a Windows event log use case where event.original contained a big XML blob.
My workaround has been to modify Kibana advanced settings to turn on
discover:searchFieldsFromSource(this will affect runtime fields and fields not in _source).