<?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: xyseries removes field line break in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498822#M85031</link>
    <description>&lt;P&gt;There are some VERY long-standing subtle bugs related to &lt;CODE&gt;makemv&lt;/CODE&gt; and similar commands when using &lt;CODE&gt;delim=&lt;/CODE&gt; where splunk "remembers" things that it should not.  This is unequivocally a bug.  Here is a search that proves that when you remove the &lt;CODE&gt;makemv&lt;/CODE&gt;, that it works:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| makeresults 
| eval _raw="value,Number
2.5,4"
| multikv
| eval value = tostring(value) + ":" + tostring(Number) + " of " + tostring(Number) 
| makemv delim=":" value
| eval Topic="C
Serviceplans" 
| eval Time="10/2019"
| xyseries Topic Time value
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 03 Dec 2019 04:44:45 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-12-03T04:44:45Z</dc:date>
    <item>
      <title>xyseries removes field line break</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498820#M85029</link>
      <description>&lt;P&gt;Hi, I have the following search where I create two fields which has a line break (Topic and value):&lt;/P&gt;

&lt;P&gt;index="example" sourcetype="trial"&lt;BR /&gt;
| stats avg(availability) as value, dc(name) as Number&lt;BR /&gt;
| eval value = tostring(value) + ":" + tostring(Number) + " of " + tostring(Number) | makemv delim=":" value&lt;BR /&gt;
| eval Topic="C" + ":" + "Serviceplans" | makemv delim=":" Topic&lt;BR /&gt;
| eval Time="10/2019" &lt;BR /&gt;
| xyseries Topic Time value&lt;/P&gt;

&lt;P&gt;When I do this xyseries will remove the linebreak from field Topic but won't do the same for value. I wanted that both fields keep the line break. &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 12:54:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498820#M85029</guid>
      <dc:creator>vini98limasilva</dc:creator>
      <dc:date>2019-11-28T12:54:13Z</dc:date>
    </item>
    <item>
      <title>Re: xyseries removes field line break</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498821#M85030</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;| makeresults 
| eval _raw="value,Number
2.5,4"
| multikv
| eval value = tostring(value) + ":" + tostring(Number) + " of " + tostring(Number) 
| makemv delim=":" value
| eval Topic="C" + ":" + "Serviceplans" 
| makemv delim=":" Topic
| eval Time="10/2019"
`comment("this is sample data")`
| eval zipped=mvzip(Topic,value)
| mvexpand zipped
| streamstats count
| eval Topic=mvindex(Topic,count -1), value=mvindex(value,count -1)
| table Time Topic value
| xyseries Topic Time value
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Hi, @vini98limasilva &lt;BR /&gt;
How about this?&lt;/P&gt;</description>
      <pubDate>Fri, 29 Nov 2019 13:06:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498821#M85030</guid>
      <dc:creator>to4kawa</dc:creator>
      <dc:date>2019-11-29T13:06:39Z</dc:date>
    </item>
    <item>
      <title>Re: xyseries removes field line break</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498822#M85031</link>
      <description>&lt;P&gt;There are some VERY long-standing subtle bugs related to &lt;CODE&gt;makemv&lt;/CODE&gt; and similar commands when using &lt;CODE&gt;delim=&lt;/CODE&gt; where splunk "remembers" things that it should not.  This is unequivocally a bug.  Here is a search that proves that when you remove the &lt;CODE&gt;makemv&lt;/CODE&gt;, that it works:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| makeresults 
| eval _raw="value,Number
2.5,4"
| multikv
| eval value = tostring(value) + ":" + tostring(Number) + " of " + tostring(Number) 
| makemv delim=":" value
| eval Topic="C
Serviceplans" 
| eval Time="10/2019"
| xyseries Topic Time value
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 03 Dec 2019 04:44:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498822#M85031</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-12-03T04:44:45Z</dc:date>
    </item>
    <item>
      <title>Re: xyseries removes field line break</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498823#M85032</link>
      <description>&lt;P&gt;Hi @to4kawa, &lt;/P&gt;

&lt;P&gt;Almost, it separated the values in different rows which wasn't exactly what I needed. Thanks for the answer anyway &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2019 12:16:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498823#M85032</guid>
      <dc:creator>vini98limasilva</dc:creator>
      <dc:date>2019-12-03T12:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: xyseries removes field line break</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498824#M85033</link>
      <description>&lt;P&gt;Thanks @woodcock, I just separated the string in different rows! Funny bug though.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2019 12:18:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/xyseries-removes-field-line-break/m-p/498824#M85033</guid>
      <dc:creator>vini98limasilva</dc:creator>
      <dc:date>2019-12-03T12:18:33Z</dc:date>
    </item>
  </channel>
</rss>

