-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Ingest Manager] Improve Endpoint data source creation and edit mode #67692
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
@parkiino @paul-tavares Could Endpoint team take on the work to match the existing custom data source component with the above designs? (@hbharding I'm assuming the designs are final :D) |
Pinging @elastic/endpoint-management (Team:Endpoint Management) |
Thanks @paul-tavares @hbharding @jen-huang - we'll get this in our priority list. |
Small updateWe removed the paneling in step 2, so posting new screenshots.
I confirmed with @caitlinbetz that this copy is good to go. |
Accidentally closed this issue |
Ahhh apologies for that. @parkiino I just realized this is the design issue. Our fault for not having the implementation issue ready for you. You can close out this issue with your PR and i'll update our spreadsheet. |
@hbharding apologies, I was under the impression that we wanted to go ahead and implement this. We can conform to this design and work with @caitlinbetz and @bfishel to finalize the text. |
We do want you to implement this! To keep things clean, I went ahead and created an implementation issue. I wanted to mark this as "done" on my end in Zube, but looks like it got caught in a weird loop. I assigned @parkiino and used the same labels, so hopefully it appears on your end. |
Duplicate Issue: #70029 Implement improved Endpoint data source creation and edit mode
The endpoint integration is different than most integrations as it doesn't use inputs and streams. In Step 3 where we ask "what data do you want to collect?", we simply say "there is nothing to configure". Instead, we want to explain to the user that a default/recommended Policy will be used, and that this policy can be configured afterwards in the Endpoint App. Any changes to the policy will cause the agent configuration to update and Fleet will deploy those changes to agents. We'll want to do something similar for the edit experience.
Test Cases:
The text was updated successfully, but these errors were encountered: