- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 7.12
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Development tools settings
- Graph settings
- Fleet settings
- i18n settings
- Logs settings
- Metrics settings
- Machine learning settings
- Monitoring settings
- Reporting settings
- Secure settings
- Search sessions settings
- Security settings
- Spaces settings
- Task Manager settings
- Telemetry settings
- Start and stop Kibana
- Access Kibana
- Securing access to Kibana
- Add data
- Upgrade Kibana
- Embed Kibana content in a web page
- Configure monitoring
- Configure security
- Production considerations
- Discover
- Dashboard
- Canvas
- Maps
- Machine learning
- Graph
- Observability
- APM
- Elastic Security
- Dev Tools
- Stack Monitoring
- Stack Management
- Fleet
- Reporting
- Alerting and Actions
- REST API
- Kibana plugins
- Accessibility
- Release notes
- Developer guide
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Display the most relevant documents per entity
editDisplay the most relevant documents per entity
editUse Top hits per entity to display the most relevant documents per entity, for example, the most recent GPS tracks per flight route. To get this data, Elasticsearch first groups your data using a terms aggregation, then accumulates the most relevant documents based on sort order for each entry using a top hits metric aggregation.
To enable top hits:
- Click Add layer, then select the Documents layer.
- Configure Index pattern and Geospatial field.
- In Scaling, select Show top hits per entity.
- Set Entity to the field that identifies entities in your documents. This field will be used in the terms aggregation to group your documents into entity buckets.
-
Set Documents per entity to configure the maximum number of documents accumulated per entity.
This setting is limited to the
index.max_inner_result_window
index setting, which defaults to 100.

Was this helpful?
Thank you for your feedback.