-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discover] Allow custom labels via index pattern fields #69908
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
FYI: @mattkime @AlonaNadler |
Is there an approach to change column names in Discover per specific saved search and not globally? |
@AlonaNadler this approach would be the first step (no prerequisites for the implementation, and multiple plugins could benefit from it without much adaption, speaking of discover, only a few lines of code), the specific saved search would be a follow up (much more prerequisites), a good second step. |
Got it, thanks @kertal that will give at least a workaround for these specific asks 👍 |
This would be very handy for visualizations. |
When can we expect this changes |
Hi, When can we expect to get this feature? /Kenneth |
@kennethlwk we're working on it, you can track the progress here: #70039 |
Closed via #70039 |
This issue describes a way to allow the user to enter a custom label in the index pattern management, and its usage in Discover.
So the user could enter a custom label for a field in the index pattern management
Usage in Discover
)
In a further step we could make this value customizable in Discover (would need much more UI adaptions), but this implementation would solve the basic problems with long filenames that cannot be customized. And it has the advantage, that it's done on a higher level, so there's no need to customize a field in every saved search.
Places not using
displayName
This should track all places that are not using
displayName
right now to present a field name, and should do so instead:Open questions
The text was updated successfully, but these errors were encountered: