Open flash1293 opened 2 months ago
Pinging @elastic/obs-ux-onboarding-team (Feature: Observability Onboarding)
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)
Pinging @elastic/fleet (Team:Fleet)
@nimarezainia @kpollich as discussed via Slack
Alternatively there could be a separate "Quickstarts" tab next to "Browse" and "Installed integrations" - this would clearly differentiate it from the actual integrations.
The Integrations UI has too much information in my view. Can we show all of the Obs. quickstart flows right at the top/beginning? That way we don't need to create another tab! Thanks
Chatted with @nimarezainia about this and before going down this path we should have the following things:
@akhileshpok feel free to discuss further with @nimarezainia if you think we should explore this further at the current time.
@nimarezainia - We have recently developed the new Obs. Quickstart onboarding flows based on customer feedback. Our intention is that we want to guide Obs. users towards these quickstarts, where applicable. We are also collecting telemetry to monitor adoption of these quickstart flows. Can we not promote the Obs. quickstart flows at the top of the Integrations page when a user filters for Observability Integrations, for both Recommended and Elastic Agent only options? Thanks
@akhileshpok we absolutely can. I don't think there is a technical concern, nor a concern about only showing this for certain types of users. In fact I would say that all the quickstarts for all solutions be displayed. We shouldn't be differentiating our users for these quickstarts imo.
We have a very full backlog on the Fleet team, given our current capacity, we are being extremely brutal in prioritization of features that the team takes on. What @flash1293 alludes to above is my concern around lack of user feedback that would help us prioritize this request against other requests we have from our active users.
As of now, all solutions have their quickstart onboarding landing pages. Could we monitor the usage and if there's any feedback from users or data around why the current placement is problematic, then certainly we can revisit this ask.
Thanks for your inputs @nimarezainia. Makes sense. We will monitor the usage of these new quickstarts and revert back when the data shows that more needs to be done.
The host, Kubernetes and soon Firehose quickstarts are helpful ways for users to get started using Elastic with certain technologies.
Currently, these are only shown on the Observability "Add data" page.
To make it easier for users to find these, they should be listed on the integrations page along with regular integrations:
Acceptance criteria: