-
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
Allow users to specify display names for fields #1896
Comments
Cool, I may use that for now. Thanks for the quick reply. |
Aliases will be definitely useful |
+1 on this. If you guide me I can try to implement it |
+1 |
+1 This would be extremely cool for aggregation of data across multiple On Mon, Apr 6, 2015 at 9:00 AM pramodupamanyu [email protected]
|
+1 |
Ability to have field aliases per visualization, search object as well as per index, and across all indexes would be really, really, awesome. Please see my comment on other issue: #2386 |
I'm new to Kibana4.. After shortDots:enable is set to true, how can I use this feature?: I mean, how to change field names using aliases in Discover or individual visualizations? (where and how to configure ?...) I googled many pages but didn't find any yet. Thanks |
👍 |
Very useful! |
👍 |
1 similar comment
👍 |
This would be very useful when combined with #706 |
+1, sooner is better. |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
If anyone is still looking for a partial work-around, if the field is numeric, you can use a "Scripted field" to alias the label: "Nice script name" ==> doc['crazy.index.name.that.is.terrible'].value via the gui "Settings" > "Indices" > [some index] > "+Add Scripted field" I am not sure what sprinkling Lucene scripts all over the place is likely to do to performance, likely nothing good, but it helped us a few cases. If anyone has anything better for labels on strings, I am in need of a solution. |
+1 |
Closing this because this use case will be addressed by the introduction of field aliases to Elasticsearch (https://www.elastic.co/guide/en/elasticsearch/reference/master/alias.html). |
This shouldn't have been closed. ES Aliases only seem to allow replacement by valid ES field names and thus don't support aliases using spaces or other odd formatting, for instance this request in the original posting... "long.elasticsearch.field.name" : "Short Name" |
Pinging @elastic/kibana-app (Team:KibanaApp) |
Thanks @Kolano! You're right. I'm reopening this issue because field aliases don't wholly address the original request. I've also changed the title to clarify the request and assigned the issue to the team that will own this enhancement. |
Thanks @cjcenizal to have reopened the issue! |
@fbaligand We created #47659 to track the effort of renaming column titles in Discover (and thus Saved Searches) separately, since this will mostly happen earlier and separated from having a way to specify display names for fields all across Kibana (which we would use this issue to track this). |
Great! |
Pinging @elastic/kibana-app-arch (Team:AppArch) |
closed via #70039 |
It would be handy to have somewhere to put some JSON to display shorter/prettier field name aliases throughout Kibana.
For example:
So instead of seeing "store.address.state" in a dropdown box or in a visualization you would see "State".
The text was updated successfully, but these errors were encountered: