Dashboards & Visualizations

Trellis panel color based on a field

kkrishnan_splun
Splunk Employee
Splunk Employee

If anyone can take a peek at this, I’d love some help. I have a need to show a status for a host, based on two sets of criteria. You can think of the criteria as a boolean truth table which I have incorporated using the eval command. The idea is to calculate a status based off of those two fields which appear to work just fine but I can’t get the trellis panels to recognize the color that’s been set. I found a similar example which I used as a model. Can anyone tell what I’m missing here?

alt text

alt text

alt text

alt text

alt text

alt text

0 Karma
1 Solution

kkrishnan_splun
Splunk Employee
Splunk Employee

Change on line 23 :


<option name="status_indicator_app.status_indicator.showOption">1</option>
into
<option name="status_indicator_app.status_indicator.showOption">3</option>

View solution in original post

robertlynch2020
Influencer

HI

I have the same issue, could you post up your code please i am finding it hard to read to screen shot.

Cheers
Rob

0 Karma

kkrishnan_splun
Splunk Employee
Splunk Employee

Change on line 23 :


<option name="status_indicator_app.status_indicator.showOption">1</option>
into
<option name="status_indicator_app.status_indicator.showOption">3</option>

robertlynch2020
Influencer

HI

I have the same issue, could you post up your code please i am finding it hard to read to screen shot.

Cheers
Rob

0 Karma
Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco &#43; Splunk! We’ve ...