-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
saved object tagging #1052
Labels
Comments
+1, maybe with ability to add tags ? |
+1 |
1 similar comment
+1 |
+1 ! |
+1 |
2 similar comments
+1 |
+1 |
Great idea. However, extend grouping to support traditional folder and subfolders; and, extend to searches and visualizations as well. |
Closed
+1 |
+1 |
1 similar comment
+1 |
Closed
Replacing with #6876 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Currently dashboards saved to Elasticsearch are stored using a single grouping and displayed as a single list. The open dashboard drop down starts to get messy when you've got hundreds of users wanting to save hundreds of dashboards across many different log sources/organizational units, both to share with others or to keep to themselves.
My initial thought was to setup a separate kibana_index for each grouping, then customize that per dashboard using a query string argument. Unfortunately, kibana_index can only be set in config.js and is not customizable per dashboard, so this idea is out.
I think there should be two top-level categorizations:
Within each overall category, dashboards should form a hierarchy or virtual folder structure allowing dashboards to be stored arbitrarily in the hierarchy, possibly to some maximum depth.
Perhaps private dashboards are just stored under a special private folder in the hierarchy.
It might look something like this:
The text was updated successfully, but these errors were encountered: