<?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 How do I Exclude null/empty fields from a lookup result where I should get a single row back in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709376#M239743</link>
    <description>&lt;P&gt;We have a lookup that has all kinds of domain (DNS) information in it with about&amp;nbsp; 60 fields like create date, ASN, name server IP,&amp;nbsp; MX IP, many of which are usually populated. But there are several fields which have no data - 10 to 20 on any given search (assuming that they are 'null'). The empty fields are likely to vary on each search. In other words some domains will have an MX record, some will not, but if they are in this lookup, they will always have a create-date.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am presenting this data on a domain lookup dashboard, using "|transpose" so that you have a table with the field name and value on a dashboard. I would like to just show a field and a value where this is returned data and filter out or not show a field which is null. Is there a way to do this?&lt;/P&gt;</description>
    <pubDate>Tue, 21 Jan 2025 21:22:25 GMT</pubDate>
    <dc:creator>donm</dc:creator>
    <dc:date>2025-01-21T21:22:25Z</dc:date>
    <item>
      <title>How do I Exclude null/empty fields from a lookup result where I should get a single row back</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709376#M239743</link>
      <description>&lt;P&gt;We have a lookup that has all kinds of domain (DNS) information in it with about&amp;nbsp; 60 fields like create date, ASN, name server IP,&amp;nbsp; MX IP, many of which are usually populated. But there are several fields which have no data - 10 to 20 on any given search (assuming that they are 'null'). The empty fields are likely to vary on each search. In other words some domains will have an MX record, some will not, but if they are in this lookup, they will always have a create-date.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am presenting this data on a domain lookup dashboard, using "|transpose" so that you have a table with the field name and value on a dashboard. I would like to just show a field and a value where this is returned data and filter out or not show a field which is null. Is there a way to do this?&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jan 2025 21:22:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709376#M239743</guid>
      <dc:creator>donm</dc:creator>
      <dc:date>2025-01-21T21:22:25Z</dc:date>
    </item>
    <item>
      <title>Re: How do I Exclude null/empty fields from a lookup result where I should get a single row back</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709385#M239747</link>
      <description>&lt;P&gt;Not sure if I fully understand the requirement. &amp;nbsp;But in general, you can assign a non-null string to those fields. &amp;nbsp;For example,&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval MX = coalesce(MX, "MX is null")&lt;/LI-CODE&gt;&lt;P&gt;The issue, I suspect, is when you transpose, all those values representing null will collapse and skew format. &amp;nbsp;Is this the problem? &amp;nbsp;If so, &amp;nbsp;you can force these values to be different, e.g.,&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval MX = coalesce(MX, "MX is null for " . FQDN)&lt;/LI-CODE&gt;&lt;P&gt;Hope. this helps.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2025 01:02:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709385#M239747</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2025-01-22T01:02:13Z</dc:date>
    </item>
    <item>
      <title>Re: How do I Exclude null/empty fields from a lookup result where I should get a single row back</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709456#M239786</link>
      <description>&lt;P&gt;Hi - thanks for the idea, Sure, I could build that into the search, true.&lt;/P&gt;&lt;P&gt;On the output dashboard what you end up with is "1 2 3 next..." on the bottom right, so you need to click through to see all possible values from the lookup that we have on hand. Often enugh there are 4-6 rows of empty fields in the result set, because the data is transpose'd. I'm looking to make the returned data more compact, if you will.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2025 14:14:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709456#M239786</guid>
      <dc:creator>donm</dc:creator>
      <dc:date>2025-01-22T14:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: How do I Exclude null/empty fields from a lookup result where I should get a single row back</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709465#M239791</link>
      <description>&lt;P&gt;If I understand you correctly you want to remove all-empty columns from your original data, right?&lt;/P&gt;&lt;PRE&gt;&amp;lt;your_search&amp;gt;&lt;BR /&gt;| transpose 0 include_empty=f&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2025 14:53:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-do-I-Exclude-null-empty-fields-from-a-lookup-result-where-I/m-p/709465#M239791</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2025-01-22T14:53:28Z</dc:date>
    </item>
  </channel>
</rss>

