Skip to content

TSVB markdown Dates, Boolean & String fields not rendering #56026

Description

@rockymia50

**Kibana version: 7.5

**Elasticsearch version:7.5

**Server OS version: macOS

**Browser version: chrome

Browser OS version:

**Original install method (e.g. download page, yum, from source, etc.):self-managed, zip download

**Describe the bug: When rendering a single result from the tree using the {{#each _all}} mustache language. Kibana will not render Dates and boolean fields, and String fields of more than 5.

DATES -> this will render 1 result of the TREE/ARRAY, but when you do it with DATES it renders the whole TREE. I want the same result that I receive with string fields. 1. If I increased the TOP field more results of the TREE/ARRAY will render the specified input.

More than 5 STRING fields -> TSVB messes up it starts to reorder your code. No matter if your code and panels read 1,2,3,4 (blocks of code or panels written in sequential order ) once you get to 5 or more... its reorders to 5,1,2,3,4 or 5,1,2,3,4,6 or worst.

BOOLEAN fields -> TRUE or False render as 0's

String fields -> mapped as type: "text" only doesn't render correctly.

The Datatypes in the mappings are declared accordingly.

Steps to reproduce:

  1. TSVB visualization with the markdown selected.

  2. Load your index using "Panel Options" tab -> data the select @timestamp on the time field

  3. Click on the Data tab and add your variables. Aggregations = Count, Add the appropriate fields either a combo or single entry of dates and text fields, grouped by "terms", top "1"

  4. If done correctly switch to the "Markdown" tab and your variable should be loaded.

  5. Enter the markdown code: ex.

{{#each _all}}
{{#with id as | id |}}
ID {{../label}}
{{/with}}

{{#with date as | date |}}
date {{../label}}
{{/with}}
{{/each}}

**Expected behavior: Code should render 1 result from each aggregation no matter the field type except "text fields" so keywords, dates, and booleans should show.

**Screenshots (if relevant):
markdown problem
markdown2

**Errors in browser console (if relevant):na

**Provide logs and/or server output (if relevant):na

**Any additional context: this visualization is not tagged as "Experimental"

Activity

  1. added
    bugFixes for quality problems that affect the customer experience
    Feature:TSVBTSVB (Time Series Visual Builder)
    Team:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//
    on Jan 28, 2020
  2. elasticmachine commented on Jan 28, 2020

    @elasticmachine
    Contributor

    Pinging @elastic/kibana-app (Team:KibanaApp)

  3. self-assigned this
    on Aug 3, 2020
  4. alexwizp commented on Aug 4, 2020

    @alexwizp
    Contributor

    From my point of view TSVB is working as designed. Let me switch to the Time Series tab to show you what kind of data you are trying to visualize in Markdown.

    image

    In my example, I have set 2 as the value for the Top field. This parameter can be set to define how many term buckets should be returned out of the overall terms list. But anyway chart is displayed for the entire timeframe. In the markdown view, everything works the same:

    image

    Here we can also see our top 2 datasets with comma separated data including: date and doc_count value for that date. doc_count is a number of docs in the bucket. Obviously we cannot apply we cannot apply boolean / date / string / etc. formatters for that.

    Now let me show you how how to display a single value instead of an entire array. Here we have 2 options:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Feature:TSVBTSVB (Time Series Visual Builder)Team:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//bugFixes for quality problems that affect the customer experiencetriage_needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions