Modern Dashboard Proportional widget status

So I'm finally diving back into proportional widgets and running into a minor issue. I have my various tables, kpis and charts added. I just noticed the Status is relaying back the number instead of the text. I wasn't sure if I was doing something wrong or if I stumbled on a minor bug. Any thoughts?

SELECT COUNT(1) AS Count_Items,
    [N].Status
FROM Orion.Nodes [N]
GROUP BY [N].Status

Find more posts tagged with

Accepted answers

All comments

jm_sysadmin

Add Status Description and use that for the Category.

SteveK

Problem with that approach is for nodes, StatusDescription contains more information than just Warning/Critical/etc... It normally includes some bit of data of what is causing the problem.

I could do a case and do a like match on the items and build out my own matrix, but I think that would break the orion icons and color scheme.

I also tried a different variant of the query, but it does royally mess up the colors and icons. I may be able to code around that, but I thought it was suppose to work with just "Orion Statuses"

adam.beedell

I'd say that formatter's not doing what it's supposed to.

There's loads of ways around this, I'll throw "Join the Status table" into the mix

But that's the point of the "Data format" "Orion Statuses" thing really.

SteveK

Thats what I was thinking. I went ahead and openned up a support case to add some visibility to it.

adam.beedell

Had a test as it'd been a while since i've touched the proportional widget

If you add the status description you lose the icons and auto-colour formatting

You can put the colours and text in bit it's a right faff. Not sure how to do the icons offhand but it's basically another table to join

Example colours:

Select
COUNT(p.Patch_Status) as [count],
p.[Patch_Status],
CASE WHEN p.Patch_Status like 'OK' then '#2ca02c'
WHEN p.Patch_Status like 'Critical' THEN '#d62728'
WHEN p.Patch_Status like 'Unknown' then '#878787'
ELSE '#d8b365'
END as [Colour]

From
(
Subquery here
)
p
Group by [Patch_Status]

Example descriptions:

SELECT COUNT(1) AS Count_Items, [N].Status, s.ShortDescription FROM Orion.Nodes [N] JOIN Orion.StatusInfo s on s.StatusId = [N].status GROUP BY [N].Status, s.ShortDescription

SteveK

I've been messing around with it a bit, and still fighting with the icon. I went the route of linking to the StatusInfo table to get the colors, but those do not line up with the ones from 'Orion Statuses' (ironic right)

Select [S].Count_Items
    , [S].Status
    , [I].StatusName
    , [I].Color
    , Concat ([I].IconPostfix,'.gif') as Icon
From Orion.StatusInfo [I]
Join 
    (SELECT COUNT(1) AS Count_Items,
        [N].Status
    FROM Orion.Nodes [N]
    --Where Place limiter here
    GROUP BY [N].Status) As [S] on [S].Status = [I].StatusID

tony.johnson

Thank you for sharing this, I am sorry to see that it is not working as expected. I have opened a bug to resolve and it is being tracked under OO-15067

adam.beedell

Thanks Tony. It can be quite difficult to get through the support structure at the moment

tony.johnson

Can you share the case number with me?

SteveK

Thank you Tony, much appreciated. I'll send the case number over. I sent it over in a DM.

adam.beedell

Steve's is the relevant one, but as you asked, my personal bugbear is that there's a requirement for a diagnostics upload for anything to pass up the line, which is super annoying for global issues: 01254222 / 01240763

Being asked for contact details on every ticket is also pretty grating after a while when I know my details are in the system and the engineers asking can see them.

It's worth mentioning as well that "SWQL is unsupported" is an official line, which means issues like this one where there's a genuine issue with a feature that uses SWQL are pretty hard to get motion on.

SteveK

Thank you again Tony. One of the leads reached out on the issue last week. They converted the issue from a feature request (as submitted by support) to a bug submission.

For a community update:

The update I received today is that the Devs determined the issue is a bug. They are currently working on the fix, but no ETA at the moment.

SteveK

So received word that the Dev team has confirmed the issue. I was informed that it will be fixed with 2023.2, but no ETA for that release yet.

adam.beedell

Good work and TY