-
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
[Logs UI] Move Log stream settings onto the Log stream page #124011
Comments
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
We're likely to request some of this information when prompting the user to configure their first curated view as per 98277. |
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
Also, we have just discovered settings are "shared" between users. When user A changes logs stream data-view, this break user B usage. As "data-view" is just visible under settings page, this make our experience quite bad :-/ |
@ebuildy thank you for reaching out. Changes to these settings are not scoped to the current user but they are space-aware. In this case, you can create a new Kibana space and change the settings there. More information about configuring the log data sources can be found in the Observability docs. |
I am really curious about usage of Kibana log stream, we have tried to specify a "big alias", but search take too much time, a simple "data view dropbox" will be awesome! |
Part of #120920
In the Settings page of the Logs app you can configure which Columns are shown in the stream but this can be hard to setup since you cannot see the stream or even an example row while editing this.
In the stream page we also have settings for things like line wrapping and text size, all of these are things users might want to customize for their own specific local use case (or "saved view" if they want to share it with others).
Further, something that is missing is being able to resize the width of the columns in the log stream, which is possible in Discover.
Discover also provides usage of Runtime fields which I'm not certain if the log stream exposes as a possible column.
Following this thread we've gotten some feedback on that the users are also seeing these limitations. (Interestingly also mentions the benefit of combining logs and visualizations on the same screen).
We should consider how we can improve this, or if this is something we should solve when saved views are in place.
One key concern is how can we allow users to both edit a view and share that exact view with others, while also allowing them to edit that view for their local machines use case in a persistent way without sharing those user specific settings with others?
The text was updated successfully, but these errors were encountered: