[Getting Started] Update and Improve Integration Dashboards

[alexfrancoeur]

In 7.16, we plan to default to the integrations page for all add data activity (elastic/kibana#111374). As a result, any new user that takes Elastic for a spin will more than likely have an agent / integration experience. First impressions are important and I believe we have an opportunity to improve ours. I know there have been some ongoing discussions around updating these dashboards over the years that follow best practices, improve aesthetics and take advantage of new capabilities (elastic/integrations#269, #27340) that would be great to implement.

As part of the getting started initiative, I'd like to prioritize this work so that new users are delighted by what we offer as part of their onboarding experience and can quickly "copy and paste" to iterate. I'd be interested in hearing this groups thoughts. I believe this could have an impact on making users successful with our extended analytics capabilities for each solution use case.

cc: @tbragin @snide @VijayDoshi @mostlyjason @rayafratkina @AlonaNadler

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[mostlyjason]

I believe @akshay-saraswat is the PM to drive improvements for dashboard guidelines since he is the PM for the ecosystem team

[akshay-saraswat]

I completely agree with you @alexfrancoeur. Without OOTB Dashboards, integrations provide less perceived value. Let's discuss and prioritize specific things that you plan to include in "getting started".

[mukeshelastic]

Hi @alexfrancoeur thanks for surfacing discussion on this topic. As a part of first user experience, we should evaluate the end to end user journeys for users choosing agent based data ingestion workflow. I see two user journeys that are owned by a specific integration, one is the integration policy configuration and other is the quality of assets. The integration policy configuration is a precursor to ingesting data and having a cleaner user experience would be crucial for higher ingestion success. So I suggest re-assessing UX for both journeys.

Having said that, it will be a good start to prioritize this effort for few frequently used data sources over all supported data sources. Doing it selectively will help us understand and develop a process that we could apply to all other integrations over time.

@akshay-saraswat For dashboards improvements, the integrations and lens team tracked gaps issue and looks like most of the issues surfaced in them were fixed. So it would be good to start moving the dashboards using the lens and other good patterns described here unless they have already been followed.

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!