-
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
CCR UI should work with data streams #65335
Comments
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
Relates to: elastic/elasticsearch#56259 |
Hi Michelle @jethr0null , I've been testing data streams in CCR today and got it working with the following setup:
I think we need to make auto-follow pattern aware of data streams. If the pattern matches a data stream in the 'remote' it should indicate so in UI. Also for the data stream to work we need to disable 'prefix' and 'suffix' input fields in the form. Otherwise, the replication will fail with an error ("a backing index name in the local and remote cluster must remain the same"). And the details flyout for the pattern should have a link to Index Management where the follower data stream is selected in the Data Streams tab. Then in the Index Management app, we need to label both follower data streams and its backing indices accordingly. |
Hi! Is there any progress on this or a plan for release? |
@stigok Sorry, no there has been no progress on this yet. |
Pinging @elastic/kibana-management (Team:Kibana Management) |
Why should we add this?
Elasticsearch is adding a new primitive called data streams. Everywhere in our UI's where a user could reference/use an Index we should allow a user to reference a data stream.
What should be changed?
CCR Top-level Menu needs to account for creating a follower data stream
Add follower index view (let's discuss how we want to represent data streams here cc @zuketo @matt-davis-elastic @cjcenizal )
Auto-follower pattern view (let's discuss how we want to represent data streams here cc @zuketo @matt-davis-elastic @cjcenizal )
I may be missing some items as I don't have any remotes enabled at the moment (I'll set one up and double-check as soon as I have time). I suspect we may also want to update how this is surfaced in monitoring (basing this on a screenshot from this blog) cc @mukeshelastic
@zuketo @matt-davis-elastic if you could please provide guidance around the user experience we're looking to provide, we can translate that into some mockups.
The text was updated successfully, but these errors were encountered: