<?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: Summarize date per week in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697468#M236934</link>
    <description>&lt;P&gt;Yup. That is one of ways to handle it. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Aug 2024 13:34:13 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2024-08-27T13:34:13Z</dc:date>
    <item>
      <title>Summarize date per week</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697428#M236922</link>
      <description>&lt;P&gt;Good day,&lt;BR /&gt;&lt;BR /&gt;I have a query to summarize data per week. Is there a way to display my tables in a better way as my dates for the path month would just be the dates in number format?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I would like to name the table Week 1, Week 2, Week 3 etc if possible.&lt;BR /&gt;&lt;BR /&gt;index=db_it_network sourcetype=pan* url_domain="&lt;A href="http://www.perplexity.ai" target="_blank"&gt;www.perplexity.ai&lt;/A&gt;" OR app=claude-base OR app=google-gemini* OR app=openai* OR app=bing-ai-base&lt;BR /&gt;| eval app=if(url_domain="&lt;A href="http://www.perplexity.ai" target="_blank"&gt;www.perplexity.ai&lt;/A&gt;", url_domain, app)&lt;BR /&gt;| table user, app, _time&lt;BR /&gt;| stats count by user app _time&lt;BR /&gt;| chart count by app _time span=1w&lt;BR /&gt;| sort app 0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 09:02:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697428#M236922</guid>
      <dc:creator>JandrevdM</dc:creator>
      <dc:date>2024-08-27T09:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: Summarize date per week</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697435#M236924</link>
      <description>&lt;LI-CODE lang="markup"&gt;index=db_it_network sourcetype=pan* url_domain="www.perplexity.ai" OR app=claude-base OR app=google-gemini* OR app=openai* OR app=bing-ai-base
| eval app=if(url_domain="www.perplexity.ai", url_domain, app)
| table user, app, _time
| eval week_num = "Week Number" . strftime(_time, "%U")
| stats count by user app week_num
| chart count by app week_num
| sort app 0&lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 27 Aug 2024 13:41:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697435#M236924</guid>
      <dc:creator>JandrevdM</dc:creator>
      <dc:date>2024-08-27T13:41:21Z</dc:date>
    </item>
    <item>
      <title>Re: Summarize date per week</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697444#M236925</link>
      <description>&lt;P&gt;1. Don't put the "table" command in that place.&amp;nbsp; It doesn't do anything useful and (in distributed setup) moves the processing to the SH layer effectively losing the advantage of parallel stats processing on indexers.&lt;/P&gt;&lt;P&gt;2. I can't quite grasp what's the point of that &lt;EM&gt;| stats | chart&lt;/EM&gt; idea. First you count, then you count the counts.&lt;/P&gt;&lt;P&gt;3. There is a &lt;EM&gt;timechart&lt;/EM&gt; command for time series.&lt;/P&gt;&lt;P&gt;4. The overal idea with &lt;EM&gt;eval&lt;/EM&gt; is OK but I'd rather use &lt;EM&gt;fieldformat&lt;/EM&gt; - this way you can freely sort based on actual underlying time data but present the data in a human-readable way.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 11:31:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697444#M236925</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-08-27T11:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: Summarize date per week</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697458#M236928</link>
      <description>&lt;P class="lia-align-left"&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks for the support.&lt;BR /&gt;&lt;BR /&gt;The reason for the&amp;nbsp;&lt;EM&gt;| stats | chart&amp;nbsp;&lt;/EM&gt;is to distinct my data by user. If I do not do this then I get multiple entries per user for each url. This allows for a user to only hit one url per week and then count them.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I will try the suggestion. I recently moved from kql to spl and will try and figure out the format for timechart and fieldformat.&lt;BR /&gt;&lt;BR /&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 12:27:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697458#M236928</guid>
      <dc:creator>JandrevdM</dc:creator>
      <dc:date>2024-08-27T12:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: Summarize date per week</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697468#M236934</link>
      <description>&lt;P&gt;Yup. That is one of ways to handle it. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 13:34:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summarize-date-per-week/m-p/697468#M236934</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-08-27T13:34:13Z</dc:date>
    </item>
  </channel>
</rss>

