Splunk Search

query search don't match on input

jtabilas
Loves-to-Learn Everything

2.png

Labels (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @jtabilas.

in the search, you have fields title, instead in fieldForLabel and fieldForValue, you have user.

They must match.

Ciao.

Giuseppe

0 Karma

jtabilas
Loves-to-Learn Everything

jtabilas_0-1688651618966.png

 

0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

This should works 

 

    <input type="multiselect" token="user">
      <label>User</label>
      <choice value="*">ALL</choice>
      <default>*</default>
      <fieldForLabel>email</fieldForLabel>
      <fieldForValue>user</fieldForValue>
      <search>
        <query>| rest /services/authentication/users splunk_server=local
| table title email
| dedup title
| rename title as user</query>
        <earliest>-24h@h</earliest>
        <latest>now</latest>
      </search>
      <valuePrefix>"</valuePrefix>
      <valueSuffix>"</valueSuffix>
      <delimiter>,</delimiter>
    </input>

 

Those fieldFor* select which filed you are using for Label (show on selection list) and real value which are set into token. Those should match to your query's output field names.

As I did rename I must use user for fieldForValue and email (or user) for fieldForLabel, but if I remove it then title is correct value for those.

r. Ismo 

0 Karma

jtabilas
Loves-to-Learn Everything

no..., the field it's title on splunk. User field don't exists

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – November 2025

  Welcome to the inaugural edition of Data Management Digest! As your trusted partner in data innovation, the ...

Splunk Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...

Introducing Value Insights (Beta): Understand the Business Impact your organization ...

Real progress on your strategic priorities starts with knowing the business outcomes your teams are delivering ...