Dashboard2.0 Charts - bug?

[akd02]

Bug in dashboards2.0 charts.json (3.1 KB)
Hi All,

is this a bug in the charts widget of Dashboard 2.0 or am i doing something wrong?

attached is a flow, and you notice that the data injected has 5 elements, yet the chart will ignore one of them and not show it.... i don't understand why.

any feedback?

[jbudd]

Can you explain what you expect the chart to look like for this data?

What does the Y axis represent?
(I confess I'm rather vague about the difference between a bar chart and a histogram, particularly if all the bars are the same width)

I notice that if you rearrange the data slightly so that similar names are grouped together:

[
    {
        "name": "Virtual Output #0",
        "state": "On hold"
    },
    {
        "name": "Virtual Output #0",
        "state": "In progress"
    },
    {
        "name": "Generic Event - 001",
        "state": "Closed"
    },
    {
        "name": "Analytics Event Alarm",
        "state": "On hold"
    },
    {
        "name": "Analytics Event Alarm",
        "state": "Closed"
    }
]

you do get 5 blocks in the chart, but I don't know what they are showing.

[akd02]

@jbudd

at does the Y axis represent?

Hi!!!!

incredibly sorry for my late reply... and appreciate your response already!

the goal of my flow is to show events by their state e.g. Closed, In progress etc.. -> that's the x-Axis

and the count of each of those states -> that's the Y-Axis

and the colors / size of each bar is for the name of the point that generated that event.

i've experimented with different settings on the Chart node... none worked apart from the one i shared never the less as you can see there is missing data "in the example i shared i inject 5 events but only 4 get are shown on the chart..... something that you seem to have "fixed" in your picture

can you share your flow so i can see what settings you chose in your example?

[jbudd]

I used your flow.

The only difference is that I rearranged the data as I showed so that items with the same name property were grouped together.

I don't know why this makes a difference, perhaps it is a bug as you suggest.