Skip to content

Conversation

wajihaparvez
Copy link
Contributor

@wajihaparvez wajihaparvez commented Mar 24, 2025

This PR adds instructions for creating an ES|QL chart from dashboards without setting up a data view.

Rel: #196658, #616

Preview: Create from dashboard

@wajihaparvez wajihaparvez self-assigned this Mar 24, 2025
@wajihaparvez wajihaparvez marked this pull request as ready for review March 25, 2025 15:08
Copy link
Contributor

@stratoula stratoula left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing

5. Select **Apply and close** to save the visualization to the dashboard.

::::{tip}
You can create an ES|QL visualization from dashboards even if you haven't specified a data view and have no existing dashboards. Just go to **Dashboards** and click **Try ES|QL**. A new dashboard is created with an ES|QL chart that you can interact with and configure like any other visualization.
Copy link
Contributor

@florent-leborgne florent-leborgne Mar 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this fits well here at the end of this section. This section explains how to add an ES|QL visualization from a dashboard, while this tip describes the "empty state" experience for when there's no dashboard yet in the Dashboards menu.

What we could do instead to avoid big changes, is to move this tip to under the first step, and say something like:

Suggested change
You can create an ES|QL visualization from dashboards even if you haven't specified a data view and have no existing dashboards. Just go to **Dashboards** and click **Try ES|QL**. A new dashboard is created with an ES|QL chart that you can interact with and configure like any other visualization.
If you don't have a dashboard nor a [data view](/explore-analyze/find-and-organize/data-views.md) yet, the **Dashboards** page offers you the possibility to **Try ES|QL** right away. By selecting this option, a dashboard is created and populated with an ES|QL visualization that you can interact with and configure using ES|QL.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@florent-leborgne it is not exactly the empty experience if you dont have a dashboard. It is if you dont have a dashboard AND a dataview. So I think is important to mention the dataview here. This is the advantage of ESQL actually. You dont need dataviews

Copy link
Contributor

@florent-leborgne florent-leborgne Mar 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, I wasn't sure if not having a data view was also a prerequisite to show this UX. I edited my suggestion. (my main issue with this tip is where it's currently located, a bit out of place in the user narrative)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense, thanks for the suggestion! I've moved the tip below the first step and tweaked the wording a bit.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanx both!

@wajihaparvez wajihaparvez enabled auto-merge (squash) March 25, 2025 19:38
@wajihaparvez wajihaparvez merged commit 1742df2 into elastic:main Mar 25, 2025
3 of 4 checks passed
@wajihaparvez wajihaparvez deleted the try-esql-without-data-views branch March 25, 2025 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants