[Fleet] Message to help users migrate to Fleet Server #95445
Comments
mostlyjason
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
|
@hbharding do you think you could provide a design for this message? |
|
Jason and I synced over zoom and I shared this initial direction (below). I think it helps to see this text within the UI - we both agreed it's quite wordy and could probably be more concise and to the point. We're going create a gdoc and work on refining the text there.
The idea is that this modal would only appear for users who had previously enrolled agents with Fleet – we can detect this because info about old agents will persist in Saved Objects after they upgrade. After users close the message, they'll see the prompt to Add a Fleet Server.
We discussed how this empty state (for Fleet Server onboarding) is slightly problematic because it replaces the agent table where users are able to see |
|
I've updated the design to account for 1) new content that's being developed in a separate google doc and 2) allowing users to still access their inactive agents while Fleet Server is not set up. We have slightly different content for cloud and self-managed users, and the agents page may look different depending on whether users previously had agents enrolled. I created a decision tree to help visualize the various scenarios, shown below. As a quick summary of what this diagram shows:
Note: One of the challenges for this issue was providing a way for users to still access inactive agents. It's not the most intuitive process since inactive agents are hidden by default. On the agents table, users need to click the Status filter button and select Inactive to see inactive agents. I had discussed an idea with @mostlyjason that maybe we should just show inactive agents by default, but since we do not currently provide a way for users to remove/forget inactive agents, we worried this would degrade the UX since most users likely do not care to see their inactive agents 100% of the time.
Self managedSee screenshotsSelf-managed migration message (only show if user had previous agents enrolled) For self-managed users who previously had agents enrolled, show the onboarding prompt inside the agents table so they can still access inactive agents For first-time self-managed users, just show the onboarding prompt CloudSee screenshotsCloud migration message (only show if user had previous agents enrolled) Most cloud users will already have a Fleet Server setup and running. If they had previous agents enrolled, they can access them by filtering for inactive agents with the status filter For cloud users who don't have a Fleet Server but did have previous agents enrolled For new cloud users who don't have a Fleet Server, just show the onboarding prompt |
|
As discussed with @hbharding it would simplify a lot the implementation if we do not make a difference between have agents before and not have agents before and show always the setup fleet server inside the agent table. |
|
@nchaulet we're going to simplify so we only have 1 state to account for. The onboarding prompt will appear on its own, i.e. not inside the agent table. Users can access inactive agents after they setup a Fleet Server, and we can explain this in documentation (cc @mostlyjason). I've updated the Figma designs to account for this. I'm not sure if you want to tackle the migration message in #95783 or a separate issue. I'll let you decide.
|
|
I created implementation issue for Nicolas here #97139. The latest Figma designs can be found here https://www.figma.com/file/G3jnu6rub6x8YExOfTWoO9/Integrations-UI-Fleet?node-id=1085%3A216572. Small update: I added a checkbox "Do not show this message again" so users have a way to access the modal again (and relevant links inside) in case they quickly dismiss it. The modal will not appear again if the checkbox is checked or if the user sets up a Fleet Server. |
|
@dikshachauhan-qasource could your team help test this migration path? FYI @EricDavisX |
|
Hi @mostlyjason We have initiated the testing around this and will update our observation under this ticket after validating each mentioned scenario. cc @EricDavisX Thanks |
|
Hi @mostlyjason We have validated this on 7.12.1 (released) Kibana upgrade to 7.13.0 BC-4 Kibana.
Screenshot: Self-managed Kibana Screenshots: Staging cloud Kibana Screenshots: Note: Please let us know if anything else is required. |
|
@amolnater-qasource for the scenario of a cloud deployment with existing agents, I see a message saying you are blocked. You can test this scenario by enrolling agents into Kibana Fleet in 7.12. You can then upgrade the deployment to 7.13 and you should see the message. Does that unblock you? Getting the pre-installed fleet server on cloud is expected. I have a separate issue to improve the landing page here #98835 |
|
Hi @mostlyjason Please refer below screenshot:
We have done this test for the lower section, Has Fleet Server- No and Has Agents previously- Yes, which we have marked as PASS. Please let us know if we are missing anything. |
|
Hi @amolnater-qasource your assessment seems right to me, and good to test on 7.13->7.14 upgrade. Please do so and we can call the testing done, apart from any issues found. |
|
Hi @EricDavisX Thanks |
|
@amolnater-qasource I understand now thanks for explaining, and yes that looks correct |
|
Hi @EricDavisX We will re-test this, whenever the upgrade issue will be fixed. Thanks |
|
Hi @EricDavisX Scenario:
Screenshots: cc: @mostlyjason |
When we launch Fleet Server, we need to help users migrate their agents from Kibana to the new Fleet Server. This will not be a turnkey migration, but something that requires manual action from users. We should add messaging in the product to help users understand what changed and how to get started with the new Fleet Server.
It should display when superusers visit the Fleet app and they have agents that were migrated from the old Fleet in Kibana. It should be dismissable per user. One call to action should point to the agent upgrade docs, which will describe the migration process.
For Elastic Cloud
Title: Enroll your agents into Fleet Server
Fleet Server is now available and it provides improved scalability and security. If you already had APM on Elastic Cloud, we've upgraded it to APM & Fleet. If not, you can add it for free.
Your existing Elastic Agents have been automatically unenrolled and have stopped sending data. To continue using Fleet, you must install the Fleet Server and the new version of Elastic Agent on each host. To see a list of inactive agents, go to the Agents page and click Status > Inactive.
This is a breaking change, which is why we are making it in a beta release. We are sorry for the inconvenience. Please share feedback if you have questions or need help.
Call to action: Fleet Server migration guide
For self-managed clusters
Title: Get ready for Fleet Server
Fleet Server is now available and it provides improved scalability and security.
Your existing Elastic Agents have been automatically unenrolled and have stopped sending data. To continue using Fleet, you must install the Fleet Server and the new version of Elastic Agent on each host. To see a list of inactive agents, go to the Agents page and click Status > Inactive.
This is a breaking change, which is why we are making it in a beta release. We are sorry for the inconvenience. Please share feedback if you have questions or need help.
Call to action: Fleet Server migration guide
Stretch:
The text was updated successfully, but these errors were encountered: