You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in the discover panel, index-pattern_ids are used when displaying the currently selected index pattern and when expanding the list of all available index patterns. This leads to not-very-user-friendly index pattern displays like [logstash-]YYYY.MM.DD. When creating a new index pattern, the title property is set to the same value as the _id, however it would be great if 1) users are allowed to set the title property and 2) the display in the discover panel is updated to use the title instead of the id. This would put index patterns in line with the same way that saved searches, visualizations and dashboards names are displayed.
I'm not sure how much work it is to allow the title to be updated on the Indices page, but a good first step might be updating the display to use title since we can at least manually update the value in Elasticsearch until it's exposed in the interface. The display update looks to be a one line change.
Thoughts?
The text was updated successfully, but these errors were encountered:
Currently in the discover panel,
index-pattern
_id
s are used when displaying the currently selected index pattern and when expanding the list of all available index patterns. This leads to not-very-user-friendly index pattern displays like[logstash-]YYYY.MM.DD
. When creating a new index pattern, thetitle
property is set to the same value as the_id
, however it would be great if 1) users are allowed to set thetitle
property and 2) the display in the discover panel is updated to use thetitle
instead of theid
. This would put index patterns in line with the same way that saved searches, visualizations and dashboards names are displayed.I'm not sure how much work it is to allow the
title
to be updated on the Indices page, but a good first step might be updating the display to usetitle
since we can at least manually update the value in Elasticsearch until it's exposed in the interface. The display update looks to be a one line change.Thoughts?
The text was updated successfully, but these errors were encountered: