Skip to content

Commit

Permalink
Update Relational Browsing screenshots
Browse files Browse the repository at this point in the history
  • Loading branch information
colmose committed Mar 21, 2018
1 parent 7fea02e commit 583d0f5
Show file tree
Hide file tree
Showing 20 changed files with 30 additions and 21 deletions.
2 changes: 1 addition & 1 deletion docs/dashboard.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ is stored in Elasticsearch. A formatted export contains the results of any appli
[[changing-the-visualization]]
== Changing the Visualization

Click the _Edit_ button image:images/EditVis.png[Pencil button] at the top right of a container to open the
Click the _Edit_ button image:images/visualization/edit-vis-pencil.png[Pencil button] at the top right of a container to open the
visualization in the <<visualize,Visualize>> page.

[float]
Expand Down
19 changes: 15 additions & 4 deletions docs/dashboard/filter_pinning.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,21 @@ filter, displaying only elements that _don't_ match, toggle the filter. Exclusio

Remove Filter image:images/filter/filter-delete.png[]:: Click this icon to remove a filter entirely.
Custom Filter image:images/filter/filter-custom.png[]:: Click this icon to display a text field where you can customize the JSON
representation of the filter and specify an alias to use for the filter name:
+
image::images/filter/filter-custom-json.png[]
+
representation of the filter and specify an alias to use for the filter name, for example, to filter the data to just the companies based in London:

image::images/relational_filter/london-companies-example-filter.png["London Companies Filter Example", align="center"]

Adding the `London Companies` label to the filter displays that label on the filter bar:

image::images/relational_filter/london-companies-filter-bar-with-label.png["London Companies Filter Bar", align="center"]

Omitting the label displays the filter query in the filter bar:

image::images/relational_filter/london-companies-filter-bar.png["London Companies Filter Bar", align="center"]

You can use a JSON filter representation to implement predicate logic, with `should` for OR, `must` for AND, and `must_not`
for NOT:

+
.OR Example
==========
Expand Down Expand Up @@ -100,5 +109,7 @@ for NOT:
==========
Click the *Done* button to update the filter with your changes.

NOTE: See {elastic-ref}/query-dsl.html[Query DSL documentation] for more information on the possibilities.

To apply any of the filter actions to all the filters currently in place, click the image:images/filter/filter-actions.png[]
*Global Filter Actions* button and select an action.
Binary file added docs/images/dashboard/edit-button.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/images/relational_filter/example_1.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/images/relational_filter/example_2.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/images/relational_filter/example_3.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/images/relational_filter/example_4.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/images/relational_filter/relational_filter_config.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/images/relational_filter/spy.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified docs/images/relational_filter/spy_debug.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed docs/images/relational_filter/spy_filterjoin.png
Binary file not shown.
File renamed without changes
2 changes: 1 addition & 1 deletion docs/management/relations.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ image::images/relations_settings/indices_settings.png["Graph of Index Patterns",
[float]
[[kibi-join-limit]]
==== Join Limit
Clicking the image:images/EditVis.png["Edit pencil"] opens the advanced setting for each relation
Clicking the image:images/visualization/edit-vis-pencil.png["Edit pencil"] opens the advanced setting for each relation
where you can set the maximum number of unique values returned from the related index pattern for that relation.

As a semi-join, these documents will be filtered based on the presence of a *non-empty* value for the `join` field
Expand Down
28 changes: 13 additions & 15 deletions docs/relational_filter.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -23,23 +23,26 @@ Both indices are <<kibi-settings-relations,configured>> so that they are joined

In the _Articles_ dashboard, the relational filter visualization is displayed as a button which indicates the number of documents in the _Companies_ dashboard that are mentioned in the articles of the current dashboard.

The screenshot below shows the button for the relation described in the example; there are 18011 companies mentioned in the 602,000 articles currently displayed:
The screenshot below shows the button for the relation described in the example; there are 18508 companies mentioned in the 646,896 articles currently displayed:

image::images/relational_filter/relational_filter_companies_source.png["Relational filter button on the Articles dashboard",align="center", width="400"]
image::images/relational_filter/relational_filter_companies_source.png["Relational filter button on the Articles dashboard",align="center", width="600"]

Clicking on the button will switch you to the _Companies_ dashboard and display the 18011 companies; the relational filter is displayed in the filter bar, as displayed below:
Clicking on the button will switch you to the _Companies_ dashboard and display the 18508 companies; the relational filter is displayed in the filter bar, as displayed below:

image::images/relational_filter/relational_filter_companies_target.png["Relational filter on the Companies dashboard",align="center", width="400"]
image::images/relational_filter/relational_filter_companies_target.png["Relational filter on the Companies dashboard",align="center", width="600"]

The relational filter visualization requires the {federate-website}[Siren Federate plugin {federate-version}]
NOTE: The relational filter visualization requires the {federate-website}[Siren Federate plugin {federate-version}]
for Elasticsearch.

[float]
[[relational_filter_config]]
=== Configuration

Click on the _Add filter_ button to create a new filter in the visualization;
the filter is defined by the following parameters:
To edit the Relational Filter configuration, click the image:images/dashboard/edit-button.png["Dashboard Edit Button"] on the Dashboard top navigation bar.

Then click the image:images/visualization/edit-vis-pencil.png["Visualization Edit Button"] on the Relational Filter visualization.

The filter is defined by the following parameters:

* _Button label_: the label of the button that will be displayed inside the visualization, e.g. `Companies -->`.
* _Custom filter label_: the label of the filter that will be displayed in the filter bar, which by default is `... related to ($COUNT) from $DASHBOARD.`. Several variables are available for customizing the label:
Expand Down Expand Up @@ -100,7 +103,7 @@ information about the raw data replace the visualization, as in this example:

image::images/relational_filter/spy.png["Spy panel of the relational filter visualization",align="center"]

This panel provides two kinds data: information about the query behind the relational filter in the `Multi Search` tab, and details about the visualization object in the `Debug` tab.
This panel provides two kinds of data: information about the query behind the relational filter in the `Multi Search` tab, and details about the visualization object in the `Debug` tab.

[float]
==== Multi Search
Expand All @@ -116,11 +119,6 @@ On the top, the time reported in `Multi search request duration` informs on how

For a particular relational filter, you can get additional information about the query that got executed.

.Filterjoin
This displays a table that provides several statistics about each join.

image::images/relational_filter/spy_filterjoin.png["Details about the filterjoin query",align="center"]

.Raw Request
The filterjoin query as sent by {kibi-name}. This uses the internal API for defining the join.

Expand All @@ -138,8 +136,8 @@ The Debug tab presents the JSON object that {kibi-name} uses for this relational
image::images/relational_filter/spy_debug.png["Debug spy panel of the relational filter visualization",align="center"]

[float]
==== Join Limit
The number of unique values returned from the `source` of the relation is limited by the `kibi:joinLimit` Advanced Setting in the management section.
==== Join Task Limit
The number of unique values returned from the `source` of the relation is limited by the `kibi:joinTaskTimeout` Advanced Setting in the management section.
These `source` values are then used to filter the documents on the `destination`. In general, the `destination` is the current dashboard.


Expand Down

0 comments on commit 583d0f5

Please sign in to comment.