Skip to content
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.

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

Update multiple data sources and add TSVB and Vega viz types #7229

Merged
merged 56 commits into from
Jul 2, 2024
Merged
Show file tree
Hide file tree
Changes from 6 commits
Commits
Show all changes
56 commits
Select commit Hold shift + click to select a range
3444cd3
Update multiple data sources and add TSVB and Vega viz types
vagimeli May 22, 2024
da5a66b
add text
vagimeli May 28, 2024
e24f0d4
Merge branch 'main' into update-multi-data
vagimeli Jun 3, 2024
4d95088
Add tutorials
vagimeli Jun 3, 2024
dbeb1fc
Merge branch 'main' into update-multi-data
vagimeli Jun 3, 2024
6045594
Add tutorials
vagimeli Jun 3, 2024
0579355
Update _dashboards/visualize/vega.md
vagimeli Jun 4, 2024
6c5d0fc
Merge branch 'main' into update-multi-data
vagimeli Jun 4, 2024
d2cf069
Update tsvb.md
vagimeli Jun 4, 2024
4d461fd
Update vega.md
vagimeli Jun 4, 2024
1f62857
Update vega.md
vagimeli Jun 4, 2024
956c07b
Update tsvb.md
vagimeli Jun 4, 2024
9886080
Update vega.md
vagimeli Jun 4, 2024
9de6631
Merge branch 'main' into update-multi-data
vagimeli Jun 4, 2024
6db6392
Address SME feedback
vagimeli Jun 4, 2024
45a51ca
Address SME feedback
vagimeli Jun 4, 2024
55dbcbf
Address SME feedback
vagimeli Jun 4, 2024
ef450d0
Address SME feedback
vagimeli Jun 4, 2024
1569b9d
Merge branch 'main' into update-multi-data
vagimeli Jun 5, 2024
1cd6f7a
Update _dashboards/visualize/tsvb.md
vagimeli Jun 21, 2024
183de14
Update _dashboards/visualize/tsvb.md
vagimeli Jun 21, 2024
69dd8a0
Update _dashboards/visualize/vega.md
vagimeli Jun 21, 2024
64da49f
Update _dashboards/visualize/vega.md
vagimeli Jun 21, 2024
5edcceb
Update _dashboards/visualize/vega.md
vagimeli Jun 21, 2024
a3b8fd6
Update _dashboards/visualize/tsvb.md
vagimeli Jun 21, 2024
334e54d
Update _dashboards/visualize/tsvb.md
vagimeli Jun 21, 2024
c39f92d
Update _dashboards/visualize/tsvb.md
vagimeli Jun 21, 2024
a96c92e
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
dd185c5
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
b8f6a75
Update _dashboards/visualize/geojson-regionmaps.md
vagimeli Jul 2, 2024
c2acdee
Update _dashboards/visualize/selfhost-maps-server.md
vagimeli Jul 2, 2024
87ad874
Update _dashboards/visualize/vega.md
vagimeli Jul 2, 2024
d7be094
Update _dashboards/visualize/visbuilder.md
vagimeli Jul 2, 2024
4a7d9ae
Update _dashboards/visualize/vega.md
vagimeli Jul 2, 2024
0429a41
Update _dashboards/visualize/vega.md
vagimeli Jul 2, 2024
20f0bb0
Update _dashboards/visualize/vega.md
vagimeli Jul 2, 2024
81ff0fe
Update _dashboards/management/multi-data-sources.md
vagimeli Jul 2, 2024
b4e52ef
Update _dashboards/management/multi-data-sources.md
vagimeli Jul 2, 2024
6813cd0
Update _dashboards/management/multi-data-sources.md
vagimeli Jul 2, 2024
49aee03
Update _dashboards/management/multi-data-sources.md
vagimeli Jul 2, 2024
6e16e10
Update _dashboards/management/multi-data-sources.md
vagimeli Jul 2, 2024
fe6e4a6
Update _dashboards/management/multi-data-sources.md
vagimeli Jul 2, 2024
8b5bee4
Update _dashboards/visualize/selfhost-maps-server.md
vagimeli Jul 2, 2024
d4327af
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
dab6b7b
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
1836276
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
c18233d
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
4811ef4
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
6d84850
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
de5e9f3
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
eb98b31
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
582b89a
Update _dashboards/visualize/tsvb.md
vagimeli Jul 2, 2024
98ae5dd
Update _dashboards/visualize/vega.md
vagimeli Jul 2, 2024
dc11e05
Update _dashboards/visualize/vega.md
vagimeli Jul 2, 2024
442ef62
Update _dashboards/visualize/vega.md
vagimeli Jul 2, 2024
c52dc36
Merge branch 'main' into update-multi-data
vagimeli Jul 2, 2024
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
11 changes: 6 additions & 5 deletions _dashboards/management/multi-data-sources.md
Original file line number Diff line number Diff line change
Expand Up @@ -203,14 +203,15 @@ When the data source feature is enabled, you can navigate to **Search Relevance*

After configuring multiple data sources, you can analyze the data from each source. Refer to the following resources for more information:

- Learn about [managing index patterns]({{site.url}}{{site.baseurl}}/dashboards/management/index-patterns/) through OpenSearch Dashboards.
- Learn about [indexing data using Index Management]({{site.url}}{{site.baseurl}}/dashboards/im-dashboards/index/) through OpenSearch Dashboards.
- Learn about how to [connect OpenSearch and Amazon S3 through OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/management/S3-data-source/).
- Learn about the [Integrations tool]({{site.url}}{{site.baseurl}}/integrations/index/), which gives you the flexibility to use various data ingestion methods and connect data from the Dashboards UI.
- [Managing index patterns]({{site.url}}{{site.baseurl}}/dashboards/management/index-patterns/) through OpenSearch Dashboards.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
- [Indexing data using Index Management]({{site.url}}{{site.baseurl}}/dashboards/im-dashboards/index/) through OpenSearch Dashboards.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
- [Connect OpenSearch and Amazon S3 through OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/management/S3-data-source/).
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
- [Integrations tool]({{site.url}}{{site.baseurl}}/integrations/index/), which gives you the flexibility to use various data ingestion methods and connect data from the OpenSearch Dashboards UI.
Copy link
Collaborator

Choose a reason for hiding this comment

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

connect "to" data?

vagimeli marked this conversation as resolved.
Show resolved Hide resolved
- Creating [Vega]({{site.url}}{{site.baseurl}}/dashboards/visualize/vega/) and [TSVB]({{site.url}}{{site.baseurl}}/dashboards/visualize/tsvb/) visualizations.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this list actually made more sense with the "Learn about" construct. As written, these are now not totally consistent, and it's not clear that the list items are all resources.

vagimeli marked this conversation as resolved.
Show resolved Hide resolved

## Limitations

The following features are not supported when using multiple data sources:

* Timeline visualization types
* Some external plugins, such as the `gantt-chart` plugin
* Certain external plugins, such as the `gantt-chart` plugin
2 changes: 1 addition & 1 deletion _dashboards/visualize/area.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: default
title: Using area charts
title: Area charts
parent: Building data visualizations
nav_order: 5
---
Expand Down
4 changes: 2 additions & 2 deletions _dashboards/visualize/gantt.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: default
title: Using Gantt charts
title: Gantt charts
parent: Building data visualizations
nav_order: 30
redirect_from:
Expand All @@ -18,7 +18,7 @@ To create a Gantt chart, perform the following steps:
1. In the visualizations menu, choose **Create visualization** and **Gantt Chart**.
1. Choose a source for the chart (e.g. some log data).
1. Under **Metrics**, choose **Event**. For log data, each log is an event.
1. Select the **Start Time** and **Duration** fields from your data set. The start time is the timestamp for the beginning of an event. The duration is the amount of time to add to the start time.
1. Select the **Start Time** and **Duration** fields from your dataset. The start time is the timestamp for the beginning of an event. The duration is the amount of time to add to the start time.
1. Under **Results**, choose the number of events to display on the chart. Gantt charts sequence events from earliest to latest based on start time.
1. Choose **Panel settings** to adjust axis labels, time format, and colors.
1. Choose **Update**.
Expand Down
6 changes: 3 additions & 3 deletions _dashboards/visualize/geojson-regionmaps.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: default
title: Using coordinate and region maps
title: Coordinate and region maps
parent: Building data visualizations
has_children: true
nav_order: 15
Expand All @@ -12,7 +12,7 @@ redirect_from:

OpenSearch has a standard set of GeoJSON files that provide a vector map with each region map. OpenSearch Dashboards also provides basic map tiles with a standard vector map to create region maps. You can configure the base map tiles using [Web Map Service (WMS)](https://www.ogc.org/standards/wms). For more information, see [Configuring WMS in OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/maptiles/).

For air gapped environments, OpenSearch Dashboards provides a self-host maps server. For more information, see [Using the self-host maps server]({{site.url}}{{site.baseurl}}/dashboards/selfhost-maps-server/)
For air-gapped environments, OpenSearch Dashboards provides a self-host maps server. For more information, see [Using the self-host maps server]({{site.url}}{{site.baseurl}}/dashboards/selfhost-maps-server/)
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Collaborator

Choose a reason for hiding this comment

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

With regard to the question in the resolved comment: Yes, it should be "self-hosted".


While you can't configure a server to support user-defined vector map layers, you can configure your own GeoJSON file and upload it for this purpose.
{: .note}
Expand All @@ -35,7 +35,7 @@ You can use [geojson.io](https://geojson.io/#map=2/20.0/0.0) to extract GeoJSON

To create your own custom vector map, upload a JSON file that contains GEO data for your customized regional maps. The JSON file contains vector layers for visualization.

1. Prepare a JSON file to upload. Make sure the file has either a .geojson or .json extension.
1. Prepare a JSON file to upload. Make sure the file has either a `.geojson` or `.json` extension.
1. On the top menu bar, go to **OpenSearch Dashboards > Visualize**.
1. Select the **Create Visualization** button.
1. Select **Region Map**.
Expand Down
2 changes: 1 addition & 1 deletion _dashboards/visualize/maps-stats-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ layout: default
title: Maps Stats API
nav_order: 20
grand_parent: Building data visualizations
parent: Using coordinate and region maps
parent: Coordinate and region maps
has_children: false
---

Expand Down
2 changes: 1 addition & 1 deletion _dashboards/visualize/maps.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: default
title: Using maps
grand_parent: Building data visualizations
parent: Using coordinate and region maps
parent: Coordinate and region maps
nav_order: 10
redirect_from:
- /dashboards/maps/
Expand Down
2 changes: 1 addition & 1 deletion _dashboards/visualize/maptiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: default
title: Configuring a Web Map Service (WMS)
grand_parent: Building data visualizations
parent: Using coordinate and region maps
parent: Coordinate and region maps
nav_order: 30
redirect_from:
- /dashboards/maptiles/
Expand Down
6 changes: 3 additions & 3 deletions _dashboards/visualize/selfhost-maps-server.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
layout: default
title: Using the self-host maps server
title: Using self-host maps servers
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
grand_parent: Building data visualizations
parent: Using coordinate and region maps
parent: Coordinate and region maps
nav_order: 40
redirect_from:
- /dashboards/selfhost-maps-server/
---

# Using the self-host maps server
# Using self-host maps servers
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

The self-host maps server for OpenSearch Dashboards allows users to access the default maps service in air-gapped environments. OpenSearch-compatible map URLs include a map manifest with map tiles and vectors, the map tiles, and the map vectors.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

Expand Down
69 changes: 69 additions & 0 deletions _dashboards/visualize/tsvb.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
---
layout: default
title: TSVB
parent: Building data visualizations
nav_order: 45
---

# TSVB

The Time-Series Visual Builder (TSVB) is a powerful data visualization tool in OpenSearch Dashboards that allows you to create detailed time-series visualizations. One of its key features is the ability to add annotations or markers at specific time points based on index data. This feature is particularly useful for making connections between multiple indexes and building visualizations that display data over time, such as flight status, delays by type, and more. TSVB currently supports the following visualization types: Area, Line, Metric, Gauge, Markdown, and Data Table.

## Creating TSVB visualizations from multiple data sources
Introduced 2.14
{: .label .label-purple }

Before proceeding, ensure that the following configurations are enabled. These can be found in `config/opensearch_dasboards.yaml`:
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

```yaml
data_source.enabled: true
vis_type_timeseries.enabled: true
```
{% include copy-curl.html %}

**Step 1: Connect data sources**

Once you have configured your YAML file, open OpenSearch Dashboards and follow these steps:

1. From the **Home** page, select **Add sample data** and then select the **Add data** button for the **Sample web logs** dataset, as shown in the following GIF.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

<img src="{{site.url}}{{site.baseurl}}/images/dashboards/tsvb.png" alt="TSVB pop-up screen" width="700"/>

2. Select **Dashboards Management** from the main menu.
3. Select **Data sources** from the left-side menu and then select the **Create data source** button.
4. From the **Create data source** page, enter the connection details and endpoint URL, as shown in the following GIF:

![Configuring and connecting data sources]({{site.url}}{{site.baseurl}}/images/dashboards/Add_datasource.gif)

**Step 2: Specify data sources**

TSVB uses your default index pattern to initialize the visualization. To change the index pattern or configure settings, follow these steps:

1. From the **Create** window, select **Panel options**.
2. Select the OpenSearch cluster from which to pull data from the **Data source** dropdown menu. In this case, choose `Source A`.
3. Enter `opensearch_dashboards_sample_data_logs` in the **Index name** field.
4. Select `@timestamp` from the **Time field** dropdown menu. This setting specifies the time range for rendering the visualization.

The following GIF shows these steps.

![Specifying data sources demo]({{site.url}}{{site.baseurl}}/images/dashboards/make_tsvb.gif)

The following image shows the TSVB visualization.

<img src="{{site.url}}{{site.baseurl}}/images/dashboards/tsvb-viz.png" alt="TSVB visualization" width="700"/>

**(Optional) Step 3: Add annotations**

Annotations are markers that can be added to time-series visualizations. Follow these steps to add annotations:

1. On the upper-left of the page, select **Time Series**.
2. Select the **Annotations** tab and then **Add data source**.
3. In the **Index** name field, specify the appropriate index. In this case, continue using the same index from the previous steps, that is, `opensearch_dashboards_sample_data_logs`.
4. From **Time** field, select `@timestamp`.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
5. In **Fields**, enter timestamp.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should 'timestamp' be in bold if they enter it as is?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@huyaboo Please provide examples of the information that the user enters in the Fields and Row template fields.
Screenshot 2024-06-21 at 2 36 21 PM

vagimeli marked this conversation as resolved.
Show resolved Hide resolved
6. In **Row** template, enter timestamp.
Copy link
Contributor

Choose a reason for hiding this comment

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

same question.

Copy link
Contributor Author

@vagimeli vagimeli Jun 28, 2024

Choose a reason for hiding this comment

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

@huyaboo What type of information does the user enter in the Fields and Row template fields. Please provide examples.

Copy link
Member

Choose a reason for hiding this comment

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

@vagimeli The user will enter in document fields. For this example, they enter in the word "timestamp" for both Fields and Row template since "timestamp" is a field in the document

vagimeli marked this conversation as resolved.
Show resolved Hide resolved

The automatically updates to display your annotations, as shown in the following image.

<img src="{{site.url}}{{site.baseurl}}images/dashboards/tsvb-with-annotations.png" alt="TSVB visualization with annotations" width="700"/>

135 changes: 129 additions & 6 deletions _dashboards/visualize/vega.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,15 @@
---
layout: default
title: Using Vega
title: Vega
parent: Building data visualizations
nav_order: 45
nav_order: 50
---

# Using Vega
# Vega

[Vega](https://vega.github.io/vega/) and [Vega-Lite](https://vega.github.io/vega-lite/) are open-source, declarative language visualization tools that you can use to create custom data visualizations with your OpenSearch data and [Vega Data](https://vega.github.io/vega/docs/data/). These tools are ideal for advanced users comfortable with writing OpenSearch queries directly. Enable the `vis_type_vega` plugin in your `opensearch_dashboards.yml` file to write your [Vega specifications](https://vega.github.io/vega/docs/specification/) in either JSON or [HJSON](https://hjson.github.io/) format or to specify one or more OpenSearch queries within your Vega specification. By default, the plugin is set to `true`. The configuration is shown in the following example. For configuration details, refer to the `vis_type_vega` [README](https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/plugins/vis_type_vega/README.md).
[Vega](https://vega.github.io/vega/) and [Vega-Lite](https://vega.github.io/vega-lite/) are open-source, declarative language visualization tools that you can use to create custom data visualizations with your OpenSearch data and [Vega Data](https://vega.github.io/vega/docs/data/). These tools are ideal for advanced users comfortable with writing OpenSearch queries directly. Enable the `vis_type_vega` plugin in your `opensearch_dashboards.yml` file to write your [Vega specifications](https://vega.github.io/vega/docs/specification/) in either JSON or [HJSON](https://hjson.github.io/) format or to specify one or more OpenSearch queries within your Vega specification. By default, the plugin is set to `true`.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

Enable the following configuration to use Vega visualizations in OpenSearch Dashboards. For configuration details, refer to the `vis_type_vega` [README](https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/plugins/vis_type_vega/README.md).

Check warning on line 12 in _dashboards/visualize/vega.md

View workflow job for this annotation

GitHub Actions / vale

[vale] _dashboards/visualize/vega.md#L12

[OpenSearch.AcronymParentheses] 'README': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
Raw output
{"message": "[OpenSearch.AcronymParentheses] 'README': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.", "location": {"path": "_dashboards/visualize/vega.md", "range": {"start": {"line": 12, "column": 250}}}, "severity": "WARNING"}

```
vis_type_vega.enabled: true
Expand All @@ -17,13 +19,15 @@

<img src="{{site.url}}{{site.baseurl}}/images/dashboards/vega-2.png" alt="Map created using Vega visualization in OpenSearch Dashboards">

## Querying from multiple data sources
## Visualizing data from multiple data sources
Introduced 2.13
{: .label .label-purple }

If you have configured [multiple data sources]({{site.url}}{{site.baseurl}}/dashboards/management/multi-data-sources/) in OpenSearch Dashboards, you can use Vega to query those data sources. Within your Vega specification, add the `data_source_name` field under the `url` property to target a specific data source by name. By default, queries use data from the local cluster. You can assign individual `data_source_name` values to each OpenSearch query within your Vega specification. This allows you to query multiple indexes across different data sources in a single visualization.

The following is an example Vega specification with `Demo US Cluster` as the specified `data_source_name`:

```
```json
{
$schema: https://vega.github.io/schema/vega/v5.json
config: {
Expand Down Expand Up @@ -190,3 +194,122 @@
}
```
{% include copy-curl.html %}

## Creating Vega visualizations with OpenSearch Dashboards
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

Before proceeding, ensure that the following configuration is enabled in your `opensearch_dashboards.yml` file:

```yml
vis_type_vega.enabled: true
```

### Step 1: Set up and connect data sources

Open OpenSearch Dashboards and follow these steps:

1. From the **Home** page, select **Add sample data**. For this tutorial, select **Sample web logs**.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved
2. From the left-side menu, navigate to **Dashboards Management** and select **Data sources**.
3. Select **Create data source connection** and then add your data source.
4. From the **Data source** dropdown menu, select the data source you created.

### Step 2: Create the visualization

1. From the left-side menu, select **Visualize**.
2. From the **Visualizations** page, select **Create Visualization** and then select **Vega** from the pop-up window, as shown in the following images.

<img src="{{site.url}}{{site.baseurl}}/images/vega.png" alt="Visualizations selection menu" width="700">

### Step 3: Add the Vega specification

1. Verify that the data source you created is specified under `data_source_name`.
2. Copy the following Vega specification.

```json
{
$schema: https://vega.github.io/schema/vega-lite/v5.json
data: {
url: {
%context%: true
%timefield%: @timestamp
index: opensearch_dashboards_sample_data_logs
data_source_name: YOUR_DATA_SOURCE_TITLE
body: {
aggs: {
1: {
date_histogram: {
field: @timestamp
fixed_interval: 3h
time_zone: America/Los_Angeles
min_doc_count: 1
}
aggs: {
2: {
avg: {
field: bytes
}
}
}
}
}
size: 0
}
}
format: {
property: aggregations.1.buckets
}
}
transform: [
{
calculate: datum.key
as: timestamp
}
{
calculate: datum[2].value
as: bytes
}
]
layer: [
{
mark: {
type: line
}
}
{
mark: {
type: circle
tooltip: true
}
}
]
encoding: {
x: {
field: timestamp
type: temporal
axis: {
title: @timestamp
}
}
y: {
field: bytes
type: quantitative
axis: {
title: Average bytes
}
}
color: {
datum: Average bytes
type: nominal
}
}
}
```

3. Select the **Update** button in the lower-right corner to visualize your data, as shown in the following GIF.

<img src="{{site.url}}{{site.baseurl}}images/make_vega.gif" alt="Visualizations selection menu">

## Resources

The following resources provide additional information about Vega visualizations in OpenSearch Dashboards:

- [Improving ease of use in OpenSearch Dashboards with Vega visualizations](https://opensearch.org/blog/Improving-Dashboards-usability-with-Vega/)
6 changes: 3 additions & 3 deletions _dashboards/visualize/visbuilder.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
layout: default
title: Using VisBuilder
title: VisBuilder
parent: Building data visualizations
nav_order: 100
redirect_from:
- /dashboards/drag-drop-wizard/
---

# Using VisBuilder
# VisBuilder

VisBuilder is an experimental feature and shouldn't be used in a production environment. For updates on its progress, or if you want to leave feedback that helps improve the feature, see the [GitHub issue](https://github.com/opensearch-project/OpenSearch-Dashboards/issues/2280).
{: .warning}
Expand All @@ -22,7 +22,7 @@ You can use the VisBuilder visualization type in OpenSearch Dashboards to create

## Try VisBuilder in the OpenSearch Dashboards playground

If you'd like to try out VisBuilder without installing OpenSearch locally, you can do so in the [Dashboards playground](https://playground.opensearch.org/app/vis-builder#/). VisBuilder is enabled by default.
If you'd like to try out VisBuilder without installing OpenSearch locally, you can do so in the [OpenSearch Dashboards playground](https://playground.opensearch.org/app/vis-builder#/). VisBuilder is enabled by default.
vagimeli marked this conversation as resolved.
Show resolved Hide resolved

## Try VisBuilder locally

Expand Down
Binary file added images/dashboards/Add_datasource.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/dashboards/make_tsvb.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/dashboards/tsvb-viz.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/dashboards/tsvb-with-annotations.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/dashboards/tsvb.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/make_vega.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/vega.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading