-
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
Customizing data table visualization column width #2516
Comments
+1 |
+1 |
+1 |
+1 in Kibana 4 and 5 the UX is horrendous in this regard. In Kibana 3 you could tweak how many chars the column was adjusted for (not sure about terminology). I miss that, and auto flexing widths for users viewport. |
+1 |
+1 please! |
+1 !!! |
Any update on this? |
+1 |
1 similar comment
+1 |
+1 - Using Data Table for custom logs causes them to be displayed longer than the screen on Chrome and requires horizontal scrolling. This makes it much more difficult to quickly scroll and gather information (say, after applying a filter of LogLevel is ERROR). Looks like quite a few people want this and it seems like low hanging fruit to me? I of course, could be wrong :) |
+1 |
1 similar comment
+1 |
Is there any update on this? This 1 tiny little feature is preventing our users from using this tool. :( |
+1 |
1 similar comment
+1 |
+125 (that's how many of our users will be using this and need this option!) |
+1 |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
Any updates? Seem like a simple thing to implement |
One functionality that I miss in both versions 3 and 4 of Kibana is the ability to select the size of the field my selves. I.e a “message” field would be large, but a “environment” , "server" or "id" field would be very small. But in Kibana this is automatically sized and a lot of space used for the small fields that instead could be used to display more of the large fields (i.e. the content of a "message" field) is wasted... Is functionality for customizing the size of fields something that will/could be added in Kibana 4? In Kibana 4 I miss this in the "Data table" visualization (could be other places as well).
The text was updated successfully, but these errors were encountered: