-
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
[Log Explorer] Group uncategorized data streams by dataset #162061
Comments
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
qq: Do we want to list them as |
Good question. I used While we generally try to not leak unnecessary Elasticsearch concepts, I see the uncategorized data streams as an intentional bridge between the ES world and the integration-based world. Does that seem like a reasonable argument? |
yes makes sense to me, at the beginning I thought it would better be consistent with the categorized dataSets, but your argument makes total sense 👍 |
## 📓 Summary Closes #162061 This implementation updates and aggregates the unmanaged datasets once they are retrieved by the state machine on initialization. I implemented this step in the state machine against doing it on the dataset service to keep the service pure and able to serve the whole response in case we need to use it on other plugins/use cases. https://github.com/elastic/kibana/assets/34506779/a5883521-6dd7-4291-9b90-0cd7665bed65 --------- Co-authored-by: Marco Antonio Ghiani <[email protected]>
## 📓 Summary Closes elastic#162061 This implementation updates and aggregates the unmanaged datasets once they are retrieved by the state machine on initialization. I implemented this step in the state machine against doing it on the dataset service to keep the service pure and able to serve the whole response in case we need to use it on other plugins/use cases. https://github.com/elastic/kibana/assets/34506779/a5883521-6dd7-4291-9b90-0cd7665bed65 --------- Co-authored-by: Marco Antonio Ghiani <[email protected]>
📓 Summary
Currently the list of "uncategorized" data streams in the dataset selector lists all data streams of the same type and dataset separately for each namespace. In order to provide a consistent experience with the integration-owned data streams, we want to only show one entry for each dataset and leave the namespace filtering up to the filter control bar.
✔️ Acceptance criteria
*
for the namespace.${type}-${dataset}-*
.🎨 Examples
Currently the same uncategorized dataset
example
in three different namespacesone
,two
, andthre
would be listed as:logs-example-one
logs-example-two
logs-example-three
Instead we want them to be listed as
logs-example-*
💡 Implementation hints
The text was updated successfully, but these errors were encountered: