<?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: Problem with evaluated fields in Summary Index populated by sistats -&amp;gt; Not accessible in reports with stats in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Problem-with-evaluated-fields-in-Summary-Index-populated-by/m-p/196758#M1739</link>
    <description>&lt;P&gt;I &lt;A href="http://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Rename" target="_blank"&gt;rename&lt;/A&gt; the psrsvd_ct_* fields I need. It works for me.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 14:09:47 GMT</pubDate>
    <dc:creator>sistemistiposta</dc:creator>
    <dc:date>2020-09-29T14:09:47Z</dc:date>
    <item>
      <title>Problem with evaluated fields in Summary Index populated by sistats -&gt; Not accessible in reports with stats</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Problem-with-evaluated-fields-in-Summary-Index-populated-by/m-p/196757#M1738</link>
      <description>&lt;P&gt;I have a query that has become quite complex and now takes several minutes to run. It seemed a perfect candidate for accelerating with a scheduled search and a summary index.&lt;/P&gt;

&lt;P&gt;The query itself uses an evaluated field to distinguish events in two overlapping time periods.&lt;BR /&gt;
When the query is run "normally" (ie. not populating the summary index) all works fine.&lt;BR /&gt;
However, when the query runs to populate the summary index, via the sistats command, the evaluated field is stored as a reserved field: psrsvd_ct_eval(T==15) and psrsvd_ct_eval(T==60).&lt;/P&gt;

&lt;P&gt;In the original query these evaluated fields were counted as 15 &amp;amp; 60 minute counts. However, when the stats command is run against the populated summary index, the values come back as zero.&lt;/P&gt;

&lt;P&gt;If I explicitly try to include the psrsvd_ct_* fields in my stats report, I get an error saying they are for internal use. I'm so close to what I need - the right data is in the index - it's just wrongly named and non-reportable.&lt;/P&gt;

&lt;P&gt;I've spent hours reading Splunk docs and googling this - there seem to be a few "workarounds" but nothing that solves my problem.&lt;/P&gt;

&lt;P&gt;Does anyone know how to resolve this?&lt;/P&gt;

&lt;P&gt;The (much simplified) basic summary index populating search looks like this:&lt;BR /&gt;
sourcetype=XX earliest=-1500m latest=-1440m location=* | where(isnotnull(error_id)) | eval T=1 | append [similar search for another period | eval T=2] | sistats count(eval(T==1)) as count1, count(eval(T==2)) as count2 by location&lt;/P&gt;

&lt;P&gt;Then, reporting on that, I use:&lt;BR /&gt;
search index=summary search_name="Summary Count" | stats count(eval(T==1)) as count1, count(eval(T==2)) as count2 by location&lt;/P&gt;

&lt;P&gt;However, count1 and count2 are always reported as 0, even though the correct data is present in the form of fields with the name/value: psrsvd_ct_eval(T==1)=num1 psrsvd_ct_eval(T==2)=num2.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:11:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Problem-with-evaluated-fields-in-Summary-Index-populated-by/m-p/196757#M1738</guid>
      <dc:creator>gavin834</dc:creator>
      <dc:date>2020-09-28T16:11:52Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with evaluated fields in Summary Index populated by sistats -&gt; Not accessible in reports with stats</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Problem-with-evaluated-fields-in-Summary-Index-populated-by/m-p/196758#M1739</link>
      <description>&lt;P&gt;I &lt;A href="http://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Rename" target="_blank"&gt;rename&lt;/A&gt; the psrsvd_ct_* fields I need. It works for me.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:09:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Problem-with-evaluated-fields-in-Summary-Index-populated-by/m-p/196758#M1739</guid>
      <dc:creator>sistemistiposta</dc:creator>
      <dc:date>2020-09-29T14:09:47Z</dc:date>
    </item>
  </channel>
</rss>

