<?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 Using multivalue field as field-list for transaction in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Using-multivalue-field-as-field-list-for-transaction/m-p/505856#M141485</link>
    <description>&lt;P&gt;When&amp;nbsp;multivalue field is given as field-list for transaction, transaction does not attempt to combine the events despite&amp;nbsp;the events have common multivalue field.&lt;/P&gt;&lt;P&gt;Example Query:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| makeresults count=4
| streamstats count
| eval abc="123"
| eval def=if(count!=2, "456", null())
| eval ghi=if(count!=1, "789", null())
| eval abc=mvdedup(mvappend(abc, def, ghi))
| transaction abc keeporphans=1 keepevicted=1&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd expect all 4 events to be combined to 1 as all events have common value of "123".&lt;/P&gt;&lt;P&gt;However this is not the case.&lt;/P&gt;&lt;P&gt;Is there any way to make this happen?&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jun 2020 01:31:01 GMT</pubDate>
    <dc:creator>Puliyo</dc:creator>
    <dc:date>2020-06-24T01:31:01Z</dc:date>
    <item>
      <title>Using multivalue field as field-list for transaction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Using-multivalue-field-as-field-list-for-transaction/m-p/505856#M141485</link>
      <description>&lt;P&gt;When&amp;nbsp;multivalue field is given as field-list for transaction, transaction does not attempt to combine the events despite&amp;nbsp;the events have common multivalue field.&lt;/P&gt;&lt;P&gt;Example Query:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| makeresults count=4
| streamstats count
| eval abc="123"
| eval def=if(count!=2, "456", null())
| eval ghi=if(count!=1, "789", null())
| eval abc=mvdedup(mvappend(abc, def, ghi))
| transaction abc keeporphans=1 keepevicted=1&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd expect all 4 events to be combined to 1 as all events have common value of "123".&lt;/P&gt;&lt;P&gt;However this is not the case.&lt;/P&gt;&lt;P&gt;Is there any way to make this happen?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jun 2020 01:31:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Using-multivalue-field-as-field-list-for-transaction/m-p/505856#M141485</guid>
      <dc:creator>Puliyo</dc:creator>
      <dc:date>2020-06-24T01:31:01Z</dc:date>
    </item>
    <item>
      <title>Re: Using multivalue field as field-list for transaction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Using-multivalue-field-as-field-list-for-transaction/m-p/505858#M141487</link>
      <description>&lt;P&gt;Guess I've figured it out myself.&lt;/P&gt;&lt;P&gt;Solution is to specify all the fields in field-list.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| transaction abc,def,ghi keeporphans=1 keepevicted=1&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 24 Jun 2020 01:42:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Using-multivalue-field-as-field-list-for-transaction/m-p/505858#M141487</guid>
      <dc:creator>Puliyo</dc:creator>
      <dc:date>2020-06-24T01:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: Using multivalue field as field-list for transaction</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Using-multivalue-field-as-field-list-for-transaction/m-p/505859#M141488</link>
      <description>&lt;P&gt;Changing the mvappend to make them a sorted single value will give you a transaction on events where abc has the same set of MV values&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval abc=mvjoin(mvsort(mvdedup(mvappend(abc, def, ghi))),",")&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;but not where any of the individual values has a common value. Not sure if that would be possible. I suspect you would have to run mvexpand on the value of abc to create separate events for that distinct value before running the transaction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jun 2020 01:50:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Using-multivalue-field-as-field-list-for-transaction/m-p/505859#M141488</guid>
      <dc:creator>bowesmana</dc:creator>
      <dc:date>2020-06-24T01:50:14Z</dc:date>
    </item>
  </channel>
</rss>

