Skip to content

[Docs] Add instructions for creating an ES|QL chart without data views #906

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Mar 25, 2025
Merged

[Docs] Add instructions for creating an ES|QL chart without data views #906

Changes from 3 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
dba58e2
Add instructions for creating ES|QL viz without data views
wajihaparvez Mar 24, 2025
dedd708
Remove trailing space
wajihaparvez Mar 24, 2025
16d7f44
Merge branch 'main' into try-esql-without-data-views
wajihaparvez Mar 25, 2025
d731669
PR feedback
wajihaparvez Mar 25, 2025
0459c89
add link
wajihaparvez Mar 25, 2025
887a271
Merge branch 'main' into try-esql-without-data-views
wajihaparvez Mar 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions explore-analyze/visualize/esorql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,9 @@ You can then **Save** and add it to an existing or a new dashboard using the sav
4. You can bind controls to your ES|QL visualizations in dashboards by creating [ES|QL controls](../dashboards/add-controls.md#add-esql-control).
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 •
edited
Loading

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 •
edited
Loading

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!

::::

## Customize the appearance of your {{esql}} visualization

Expand Down
Loading