<?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: summary index in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583570#M8690</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/238710"&gt;@mm12&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;at first you have to index metrics from your servers using dedicated Add-Ons like&amp;nbsp;Splunk_TA_nix (&lt;A href="https://splunkbase.splunk.com/app/833/" target="_blank"&gt;https://splunkbase.splunk.com/app/833/&lt;/A&gt;) for Linux systems or Splunk_TA_Windows (&lt;A href="https://splunkbase.splunk.com/app/742/" target="_blank"&gt;https://splunkbase.splunk.com/app/742/&lt;/A&gt;)&amp;nbsp;for Windows Servers.&lt;/P&gt;&lt;P&gt;Then you you could schedule every week one or (better) more searches to record in a summary index (called e.g. summary_statistics) the average calculation for each metric, like the following:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=os sourcetype=cpu
| stats earliest(_time) AS _time avg(cpu) AS value BY host
| eval metric="cpu_utilization"
| table _time host metric value 
| collect index=summary_statistics&lt;/LI-CODE&gt;&lt;P&gt;or&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=os sourcetype=top
| stats earliest(_time) AS _time avg(memory) AS value BY host
| eval metric="memory"
| table _time host metric value 
| collect index=summary_statistics&lt;/LI-CODE&gt;&lt;P&gt;etc...&lt;/P&gt;&lt;P&gt;In this way you'll have in the summary index four informations:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;date (only one for each week),&lt;/LI&gt;&lt;LI&gt;host,&lt;/LI&gt;&lt;LI&gt;metric, the metric you want to analyze,&lt;/LI&gt;&lt;LI&gt;value, the value for the metric.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Then you can run a search on the summary index:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=summary_statistics
| bin _time span=1w
| eval TimeStamp=strftime(_time),"%Y-%m-%d")
| table Timestamp host metric value&lt;/LI-CODE&gt;&lt;P&gt;About the searches to schedule, I hint to se in dedicated apps like Splunk App for Linux and Unix (&lt;A href="https://splunkbase.splunk.com/app/273/" target="_blank"&gt;https://splunkbase.splunk.com/app/273/&lt;/A&gt;) to have all the parametrs to use in the searches.&lt;/P&gt;&lt;P&gt;&amp;nbsp;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Thu, 03 Feb 2022 14:56:40 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2022-02-03T14:56:40Z</dc:date>
    <item>
      <title>How to create a summary index?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583561#M8687</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;
&lt;P&gt;I want to create summary index for the below OS metrics process . How to achieve this.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;1.Avg CPU per week*&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;2.Avg memory per week*&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;3. Avg /var/log/ % used, per week*&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;4. # processes running, per week*&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 00:36:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583561#M8687</guid>
      <dc:creator>mm12</dc:creator>
      <dc:date>2022-02-17T00:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: summary index</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583566#M8688</link>
      <description>&lt;P&gt;Start by creating a report that provides that information from your events&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 14:43:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583566#M8688</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2022-02-03T14:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: summary index</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583569#M8689</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/225168"&gt;@ITWhisperer&lt;/a&gt;&amp;nbsp; I can able to write separate queries for example&amp;nbsp;&lt;/P&gt;&lt;P&gt;For Avg CPU&lt;/P&gt;&lt;P&gt;| mstats avg(cpu_metric.pctIdle) AS "cpu_idle" WHERE index=linux_os_metrics by host CPU span=1m&lt;BR /&gt;| eval "cpu%_Utilized"=round(100-cpu_idle, 2)&lt;BR /&gt;|search CPU=all |fields - CPU cpu_idle | timechart span=1m avg(cpu%_Utilized) by host&lt;/P&gt;&lt;P&gt;But how to combine that in summary index&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Manju&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 14:52:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583569#M8689</guid>
      <dc:creator>mm12</dc:creator>
      <dc:date>2022-02-03T14:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: summary index</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583570#M8690</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/238710"&gt;@mm12&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;at first you have to index metrics from your servers using dedicated Add-Ons like&amp;nbsp;Splunk_TA_nix (&lt;A href="https://splunkbase.splunk.com/app/833/" target="_blank"&gt;https://splunkbase.splunk.com/app/833/&lt;/A&gt;) for Linux systems or Splunk_TA_Windows (&lt;A href="https://splunkbase.splunk.com/app/742/" target="_blank"&gt;https://splunkbase.splunk.com/app/742/&lt;/A&gt;)&amp;nbsp;for Windows Servers.&lt;/P&gt;&lt;P&gt;Then you you could schedule every week one or (better) more searches to record in a summary index (called e.g. summary_statistics) the average calculation for each metric, like the following:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=os sourcetype=cpu
| stats earliest(_time) AS _time avg(cpu) AS value BY host
| eval metric="cpu_utilization"
| table _time host metric value 
| collect index=summary_statistics&lt;/LI-CODE&gt;&lt;P&gt;or&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=os sourcetype=top
| stats earliest(_time) AS _time avg(memory) AS value BY host
| eval metric="memory"
| table _time host metric value 
| collect index=summary_statistics&lt;/LI-CODE&gt;&lt;P&gt;etc...&lt;/P&gt;&lt;P&gt;In this way you'll have in the summary index four informations:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;date (only one for each week),&lt;/LI&gt;&lt;LI&gt;host,&lt;/LI&gt;&lt;LI&gt;metric, the metric you want to analyze,&lt;/LI&gt;&lt;LI&gt;value, the value for the metric.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Then you can run a search on the summary index:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=summary_statistics
| bin _time span=1w
| eval TimeStamp=strftime(_time),"%Y-%m-%d")
| table Timestamp host metric value&lt;/LI-CODE&gt;&lt;P&gt;About the searches to schedule, I hint to se in dedicated apps like Splunk App for Linux and Unix (&lt;A href="https://splunkbase.splunk.com/app/273/" target="_blank"&gt;https://splunkbase.splunk.com/app/273/&lt;/A&gt;) to have all the parametrs to use in the searches.&lt;/P&gt;&lt;P&gt;&amp;nbsp;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 14:56:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583570#M8690</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-02-03T14:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: summary index</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583574#M8691</link>
      <description>&lt;P&gt;It depends what it is you want in your summary index&lt;/P&gt;&lt;P&gt;You could have a report for each metric and add them all to the same summary index as events for each minute. You could distinguish which metric came from which report using the search_name added to the event by the summary index process&lt;/P&gt;&lt;P&gt;If you want a single event per minute with all the stats for all the hosts, you need to construct a report that gives you that information, then schedule it and enable summary indexing to the summary index of your choice. Note that summary indexes have to be created before they can be used.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 15:04:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/583574#M8691</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2022-02-03T15:04:56Z</dc:date>
    </item>
    <item>
      <title>Re: summary index</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/585138#M8707</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;| mstats avg(cpu_metric.pctIdle) AS "cpu_idle" WHERE index=os_metric bY host&lt;BR /&gt;| search&lt;BR /&gt;[| inputlookup lookup_mapping&lt;BR /&gt;| search service="os_metric" host= * | table host]&lt;BR /&gt;| eval "cpu_usage"=round(100-cpu_idle, 2)&lt;BR /&gt;| sitimechart avg(cpu_usage) as "cpu_usage" by host&lt;/P&gt;&lt;P&gt;I used the above query to check the CPU usage and schedule it as report and enable the &lt;STRONG&gt;summary Metric index&lt;/STRONG&gt;&lt;BR /&gt;I got three fields like psrsvd_ct_cpu_usage, psrsvd_nc_cpu_usage and&lt;BR /&gt;psrsvd_sm_cpu_usage. Now I need to query the summary index to use it in dashboard. How to achieve that.&lt;/P&gt;&lt;P&gt;Can anyone help me on this please.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 10:21:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/How-to-create-a-summary-index/m-p/585138#M8707</guid>
      <dc:creator>mm12</dc:creator>
      <dc:date>2022-02-15T10:21:22Z</dc:date>
    </item>
  </channel>
</rss>

