Kibana: [Ingest Manager] Improve getting started UX for enabling Fleet for on prem.
It can be difficult to run Fleet locally / on prem because of the security requirements. We need to provide better information on what's required to run Fleet, and how to set everything up. Currently, the page looks like this:
hbharding
All 5 comments
Pinging @elastic/ingest-management (Team:Ingest Management)
elasticmachine
on 28 May 2020
Update:
cc @nchaulet @ruflin @mostlyjason @jen-huang @ph
We want to improve the information we provide to users when they have missing requirements for running Fleet. I used the "prerequisites" section from our docs site to gather this information, and for the most part, it is the same. We should use the same links for "Elasticsearch security", "API key service", etc. as we do in our docs.
The requirements appear as bullet point items, but we're using colored icons instead to represent whether or not the requirement is met. In the screenshot, you'll notice that Elasticsearch security is enabled, but API key service is not. Once all the requirements are met, the user will be directed to the Fleet page where they will be able to add and enroll agents.
Below the requirements, we also provide a copyable code snippet that users can paste directly into their configuration file.
hbharding
on 25 Jun 2020
@hbharding what about spaces being enabled and ingest manager enabled in that list? https://github.com/elastic/endpoint-app-team/issues/296
mostlyjason
on 7 Jul 2020
@mostlyjason If Ingest Manager isn't enabled as a feature in that space, the entire app won't be visible in that space so they wouldn't be able to reach this page in Fleet.
jen-huang
on 7 Jul 2020
Good point thanks @jen-huang
mostlyjason
on 8 Jul 2020
Related issues
bradvido
路
3Comments
ynux
路
3Comments
treussart
路
3Comments
MaartenUreel
路
3Comments
timmolter
路
3Comments
Most helpful comment
Update:
cc @nchaulet @ruflin @mostlyjason @jen-huang @ph
Video explanation
Figma link
We want to improve the information we provide to users when they have missing requirements for running Fleet. I used the "prerequisites" section from our docs site to gather this information, and for the most part, it is the same. We should use the same links for "Elasticsearch security", "API key service", etc. as we do in our docs.
The requirements appear as bullet point items, but we're using colored icons instead to represent whether or not the requirement is met. In the screenshot, you'll notice that Elasticsearch security is enabled, but API key service is not. Once all the requirements are met, the user will be directed to the Fleet page where they will be able to add and enroll agents.
Below the requirements, we also provide a copyable code snippet that users can paste directly into their configuration file.