You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a user visits the Agents page after starting a new deployment, its not obvious what step they need to take next. They see the Elastic Cloud agent, but they aren't familiar with what that is yet. Also, they can't use it for anything because we don't allow other integrations to run there. Previously, we had an empty state screen making it obvious that users need to add an agent, but that is not visible on ESS/ECE.
When a user visits this page for the first time, can we offer a short intro to Fleet & Elastic Agent, and make it more obvious that the next step is adding an agent? Perhaps something like this?
Welcome to Fleet! To get started, [add an Elastic Agent] to a server, laptop or other host. When you enroll an agent into Fleet, you can see its status and update it here. You can then add integrations to monitor your host or protect it from security threats.
Current page:
The text was updated successfully, but these errors were encountered:
mostlyjason
changed the title
[Fleet] Show empty state screen on Agents page for ESS/ECE
[Fleet] Improve onboarding on Agents page for ESS/ECE
Apr 30, 2021
Currently, when a user visits the Agents page after starting a new deployment, its not obvious what step they need to take next. They see the Elastic Cloud agent, but they aren't familiar with what that is yet. Also, they can't use it for anything because we don't allow other integrations to run there. Previously, we had an empty state screen making it obvious that users need to add an agent, but that is not visible on ESS/ECE.
When a user visits this page for the first time, can we offer a short intro to Fleet & Elastic Agent, and make it more obvious that the next step is adding an agent? Perhaps something like this?
Current page:
The text was updated successfully, but these errors were encountered: