Skip to content
Merged
Changes from all commits
Commits
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
15 changes: 3 additions & 12 deletions explore-analyze/visualize/custom-visualizations-with-vega.md
Original file line number Diff line number Diff line change
Expand Up @@ -1126,7 +1126,7 @@ Learn more about {{kib}} extension, additional **Vega** resources, and examples.
* [preview] Using the Elastic Map Service in Vega maps
* Additional tooltip styling
* Advanced setting to enable URL loading from any domain
* Debugging support using the {{kib}} inspector or browser console
* Debugging support using the {{kib}} inspector
* (Vega only) Expression functions which can update the time range and dashboard filters


Expand Down Expand Up @@ -1165,7 +1165,7 @@ padding: {
To learn more, read about [Vega autosize](https://vega.github.io/vega/docs/specification/#autosize) and [Vega-Lite autosize](https://vega.github.io/vega-lite/docs/size.html).

::::{note}
Autosize in Vega-Lite has [several limitations](https://vega.github.io/vega-lite/docs/size.html#limitations) which can affect the height and width of your visualization, but these limitations do not exist in Vega. If you need full control, convert your spec to Vega using the [browser console](#vega-browser-debugging-console) `VEGA_DEBUG.vega_spec` output. To disable these warnings, you can [add extra options to your spec](#vega-additional-configuration-options).
Autosize in Vega-Lite has [several limitations](https://vega.github.io/vega-lite/docs/size.html#limitations) which can affect the height and width of your visualization, but these limitations do not exist in Vega.
::::


Expand Down Expand Up @@ -1472,7 +1472,7 @@ The runtime data is read from the [runtime scope](https://vega.github.io/vega/do
:screenshot:
:::

To debug more complex specs, access to the `view` variable. For more information, refer to the [Vega browser debugging process](#vega-browser-debugging-console).
To debug more complex specs, copy the Vega spec from the **Spec** tab and use the [online Vega Editor](https://vega.github.io/editor/) to debug it.


##### Asking for help with a Vega spec [asking-for-help-with-a-vega-spec]
Expand All @@ -1487,15 +1487,6 @@ Because of the dynamic nature of the data in {{es}}, it is hard to help you with
To copy the response, click **Copy to clipboard**. Paste the copied data to [gist.github.com](https://gist.github.com/), possibly with a .json extension. Use the [raw] button, and share that when asking for help.


#### Browser debugging console [vega-browser-debugging-console]

[preview] Use browser debugging tools (for example, F12 or Ctrl+Shift+J in Chrome) to inspect the `VEGA_DEBUG` variable:

* `view` — Access to the Vega View object. See [Vega Debugging Guide](https://vega.github.io/vega/docs/api/debugging/) on how to inspect data and signals at runtime. For Vega-Lite, `VEGA_DEBUG.view.data('source_0')` gets the pre-transformed data, and `VEGA_DEBUG.view.data('data_0')` gets the encoded data. For Vega, it uses the data name as defined in your Vega spec.
* `vega_spec` — Vega JSON graph specification after some modifications by {{kib}}. In case of Vega-Lite, this is the output of the Vega-Lite compiler.
* `vegalite_spec` — If this is a Vega-Lite graph, JSON specification of the graph before Vega-Lite compilation.


#### (Vega only) Expression functions which can update the time range and dashboard filters [vega-expression-functions]

{{kib}} has extended the Vega expression language with these functions. These functions will trigger new data to be fetched, which by default will reset Vega signals. To keep signal values set `restoreSignalValuesOnRefresh: true` in the Vega config.
Expand Down