Excluded fields

Excluded Fields Help

Excluded Fields Help

All fields are by default retrieved and are available inside the "_source" object of each hit. Thanks to the source filtering API of Elasticsearch, you can choose which fields are actually retrieved for different visualisations. The value needs to be a JSON object. Top level properties are visualisation types. Currently supported types:


Examples

Below is an example where both options (all, kibi_graph_browser) or just one option is used

Exclusions of a single field
{ "all": { "exclude": "user" }, "kibi_graph_browser": { "exclude": "city" } }
{ "all": { "exclude": "user" } }
{ "kibi_graph_browser": { "exclude": "city" } }
Exclusions with a path pattern
{ "all": { "exclude": ["obj1.*", "*.value"] }, "kibi_graph_browser": { "exclude": ["obj2.*", "*.value"] } }
{ "all": { "exclude": ["obj1.*", "*.value"] } }
{ "kibi_graph_browser": { "exclude": [ "obj2.*", "*.value"] } }
Complete control with exclusions and inclusion
{ "all": { "exclude": "obj1.*", "include": "obj2.*.val" }, "kibi_graph_browser": { "exclude": "obj2.*", "include": "obj3.*.val" } }
{ "all": { "exclude": "obj1.*", "include": "obj2.*.val" } }
{ "kibi_graph_browser": { "exclude": "obj2.*", "include": "obj3.*.val" } }

By default, all fields are retrieved to populate results table. Sometimes however some fields can be very large and seriously affect performance. This can be often the case when you have materialized one to many relationships, e.g., an entity having many nested entities. Those fields are still useful for searching or analytics but not in a result table.

Use this setting to decide what to include or exclude in the data retrieved from the Elasticsearch index.
If empty, all fields are retrieved.

{{ sourceFiltering | json }}