Dashboards & Visualizations

How to resolve this Multiselect Filter Issue?

jason_hotchkiss
Communicator

I have the following XML

 

     <input type="multiselect" token="exclude_user" searchWhenChanged="true">
        <label>Exclude User</label>
        <valuePrefix>"</valuePrefix>
        <valueSuffix>"</valueSuffix>
        <delimiter>, </delimiter>
        <fieldForLabel>user</fieldForLabel>
        <fieldForValue>user</fieldForValue>
        <search base="filtered">
          <query>| stats values(User) as user
| mvexpand user
| dedup user</query>
        </search>
        <choice value="SYSTEM">SYSTEM</choice>
        <choice value="-">NONE</choice>
        <default>SYSTEM</default>
        <initialValue>SYSTEM</initialValue>
      </input>

 


The filter is setup as an exclusion filter using a post processing search in conjunction with the base search, such as:

| search NOT User IN ($exclude_user$)

The multiselect works, until the value of "NONE" is selected which inputs the values of

| search NOT User IN (" ") into the post processing search.

Text below the filter displays, "Duplicate values causing conflict".  This doesn't prevent the search from completing, and the results I receive are what I expect to be returned.

It would be ideal for the message below the multiselect filter to not be displayed.  Anyone have a suggestion on how I can get rid of it?

I have tried the following:

Adding | dedup User to the post processing search.
Changing the fieldForLabel value to " " and NONE

Not sure what to try next.  Thanks in advanced.

Labels (3)
0 Karma
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...