<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why is the text input not filtering results correctly in the dashboard? in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414104#M27222</link>
    <description>&lt;P&gt;Adding the token prefix &lt;CODE&gt;DatastoreName=*_&lt;/CODE&gt; fixed the issue.  Thank you for your help.  I will definitely do the same for my other tokens since they are related to fields.&lt;/P&gt;</description>
    <pubDate>Fri, 29 Jun 2018 15:29:36 GMT</pubDate>
    <dc:creator>gbwilson</dc:creator>
    <dc:date>2018-06-29T15:29:36Z</dc:date>
    <item>
      <title>Why is the text input not filtering results correctly in the dashboard?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414100#M27218</link>
      <description>&lt;P&gt;So I have a dashboard with 3 different inputs.  I noticed something really weird with my text input.  If I enter the number 22 into my text input search, results on my dashboard stats table include 21, &lt;STRONG&gt;22&lt;/STRONG&gt;, 24, 25, 27, 28, 29, 33, etc.  &lt;/P&gt;

&lt;P&gt;Why is my text input showing me results that don't match the text input exactly?&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/5293i4B3BA42B57B1DC57/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Below is my query for the stats table:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;(index=cms_vm) $arrayfield$ $lun$ $datacenter$
| dedup VM
| eval DatastoreName=replace(DatastoreName,".+_(\d+)$","\1") 
| eval StorageArray=replace(StorageArray,"^[^_]*_[^_]*\K.*$","")
| eval VM=upper(VM)
| eval StorageArray=upper(StorageArray)
| join type=outer VM [search index="cms_app_server" | fields VM Application]
| table VM OperatingSystem_Code Datacenter StorageArray DatastoreName Application
| rename OperatingSystem_Code AS "Operating System", StorageArray AS "Storage Array", DatastoreName AS "LUN"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any help would be appreciated as I can't seem to pinpoint why this is occurring.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 14:20:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414100#M27218</guid>
      <dc:creator>gbwilson</dc:creator>
      <dc:date>2018-06-29T14:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the text input not filtering results correctly in the dashboard?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414101#M27219</link>
      <description>&lt;P&gt;It will match any event with the string &lt;CODE&gt;22&lt;/CODE&gt; in the raw event. I'm guessing it matches a 22 somewhere else then where you want to match it (the lun number), like in a timestamp or so? So you may need to create a more advanced filtering rather than just plain text search strings.&lt;BR /&gt;
Isn't that 'lun' info available in a specific field?&lt;/P&gt;

&lt;P&gt;Otherwise post some sample data so we can help improve your query.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 14:37:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414101#M27219</guid>
      <dc:creator>FrankVl</dc:creator>
      <dc:date>2018-06-29T14:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the text input not filtering results correctly in the dashboard?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414102#M27220</link>
      <description>&lt;P&gt;@FrankVI how would you recommend doing more advanced filtering?  I also tried creating a multiselect the dynamically updates based on the first two inputs.  It still will display results that should not be appearing.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 15:04:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414102#M27220</guid>
      <dc:creator>gbwilson</dc:creator>
      <dc:date>2018-06-29T15:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the text input not filtering results correctly in the dashboard?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414103#M27221</link>
      <description>&lt;P&gt;It would help if you could share some info on what the data looks like. But from what the rest of your search looks like, I'm guessing the &lt;CODE&gt;DatastoreName&lt;/CODE&gt; field actually contains the LUN number that you want to filter for?&lt;/P&gt;

&lt;P&gt;So you could try something as simple as putting the following into the token prefix field:&lt;BR /&gt;
&lt;CODE&gt;DatastoreName = *_&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Such that the search will be:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; (index=cms_vm) $arrayfield$ DatastoreName = *_$lun$ $datacenter$ | ...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;PS: you might want to do similar things for the other tokens as well, since it looks like also datacenter and array are actually related to fields?&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 15:22:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414103#M27221</guid>
      <dc:creator>FrankVl</dc:creator>
      <dc:date>2018-06-29T15:22:43Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the text input not filtering results correctly in the dashboard?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414104#M27222</link>
      <description>&lt;P&gt;Adding the token prefix &lt;CODE&gt;DatastoreName=*_&lt;/CODE&gt; fixed the issue.  Thank you for your help.  I will definitely do the same for my other tokens since they are related to fields.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 15:29:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414104#M27222</guid>
      <dc:creator>gbwilson</dc:creator>
      <dc:date>2018-06-29T15:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the text input not filtering results correctly in the dashboard?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414105#M27223</link>
      <description>&lt;P&gt;I have been having the same problem when building one of my projects, but then I was fixed, the more problems I got with the design, but I found a good option for me, just bought several mockups from &lt;A href="https://webdesignblog.info/html-css-templates/bootstrap-4-admin-dashboards/"&gt;https://webdesignblog.info/html-css-templates/bootstrap-4-admin-dashboards/&lt;/A&gt; it was very nice at the result. &lt;/P&gt;</description>
      <pubDate>Sun, 01 Jul 2018 20:28:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Why-is-the-text-input-not-filtering-results-correctly-in-the/m-p/414105#M27223</guid>
      <dc:creator>Flex223</dc:creator>
      <dc:date>2018-07-01T20:28:33Z</dc:date>
    </item>
  </channel>
</rss>

