<?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: appendcols issue in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-are-we-having-an-appendcols-issue/m-p/604059#M210133</link>
    <description>&lt;P&gt;With your query the data shows correctly.&lt;/P&gt;&lt;P&gt;Thank you very much!!&lt;/P&gt;</description>
    <pubDate>Fri, 01 Jul 2022 01:09:40 GMT</pubDate>
    <dc:creator>simon1524</dc:creator>
    <dc:date>2022-07-01T01:09:40Z</dc:date>
    <item>
      <title>Why are we having an appendcols issue?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-we-having-an-appendcols-issue/m-p/603900#M210083</link>
      <description>&lt;P&gt;There is something wrong with the data output by using apendcols. The data of Total_Actual is blank from 02-2022. But actually there has data all of months. May I know what's the reason..?&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index=sourceA

PRIORITY="High" OR
PRIORITY="Medium" OR
PRIORITY="Low"
WAS_CRITICAL="yes"
| eval _time=strptime(FIRST_SOLVED_DATE,"%Y-%m-%d %H:%M:%S.%N")
| timechart span=1mon count as Total

| appendcols [search index=sourceA

PRIORITY="Critical"
| eval _time=strptime(FIRST_SOLVED_DATE,"%Y-%m-%d %H:%M:%S.%N")
| timechart span=1mon count as Total_Actual]
| eval Rate_%=round((Total_Actual/Total)*100, 2)
| table _time, Total, Total_Actual, Rate_%
| tail 12
| sort _time&lt;/LI-CODE&gt;
&lt;P&gt;OUTPUT&lt;/P&gt;
&lt;TABLE border="0" width="256" cellspacing="0" cellpadding="0"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="64" height="17"&gt;_time&lt;/TD&gt;
&lt;TD width="64"&gt;Total&lt;/TD&gt;
&lt;TD width="64"&gt;Total_Actual&lt;/TD&gt;
&lt;TD width="64"&gt;Rate_%&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2021-07-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;76&lt;/TD&gt;
&lt;TD&gt;64&lt;/TD&gt;
&lt;TD&gt;84.21&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2021-08-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;74&lt;/TD&gt;
&lt;TD&gt;51&lt;/TD&gt;
&lt;TD&gt;68.92&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2021-09-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;81&lt;/TD&gt;
&lt;TD&gt;45&lt;/TD&gt;
&lt;TD&gt;55.56&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2021-10-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;75&lt;/TD&gt;
&lt;TD&gt;71&lt;/TD&gt;
&lt;TD&gt;94.67&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2021-11-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;118&lt;/TD&gt;
&lt;TD&gt;58&lt;/TD&gt;
&lt;TD&gt;49.15&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2021-12-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;101&lt;/TD&gt;
&lt;TD&gt;105&lt;/TD&gt;
&lt;TD&gt;103.96&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2022-01-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;81&lt;/TD&gt;
&lt;TD&gt;86&lt;/TD&gt;
&lt;TD&gt;106.17&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2022-02-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;95&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2022-03-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;85&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2022-04-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;96&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2022-05-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;106&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD height="17"&gt;2022-06-01T00:00:00.000+0200&lt;/TD&gt;
&lt;TD&gt;141&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Thu, 30 Jun 2022 13:33:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-we-having-an-appendcols-issue/m-p/603900#M210083</guid>
      <dc:creator>simon1524</dc:creator>
      <dc:date>2022-06-30T13:33:08Z</dc:date>
    </item>
    <item>
      <title>Re: appendcols issue</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-we-having-an-appendcols-issue/m-p/603924#M210092</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/247340"&gt;@simon1524&lt;/a&gt;&amp;nbsp;- Try this query instead:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=sourceA
| eval _time=strptime(FIRST_SOLVED_DATE,"%Y-%m-%d %H:%M:%S.%N")

| timechart span=1mon count(eval((PRIORITY="High" OR PRIORITY="Medium" OR PRIORITY="Low") AND WAS_CRITICAL="yes")) as Total, count(eval(PRIORITY="Critical")) as Total_Actual

| eval Rate_%=round((Total_Actual/Total)*100, 2)
| table _time, Total, Total_Actual, Rate_%
| tail 12
| sort _time&lt;/LI-CODE&gt;&lt;P&gt;Single timechart command without appendpipe should give you the results.&lt;/P&gt;&lt;P&gt;This query is much more robust and performance effective.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps!!! Karma/upvote would be appreciated!!!&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 09:47:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-we-having-an-appendcols-issue/m-p/603924#M210092</guid>
      <dc:creator>VatsalJagani</dc:creator>
      <dc:date>2022-06-30T09:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: appendcols issue</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-are-we-having-an-appendcols-issue/m-p/604059#M210133</link>
      <description>&lt;P&gt;With your query the data shows correctly.&lt;/P&gt;&lt;P&gt;Thank you very much!!&lt;/P&gt;</description>
      <pubDate>Fri, 01 Jul 2022 01:09:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-are-we-having-an-appendcols-issue/m-p/604059#M210133</guid>
      <dc:creator>simon1524</dc:creator>
      <dc:date>2022-07-01T01:09:40Z</dc:date>
    </item>
  </channel>
</rss>

