<?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: Trend scenario II- three dimensional data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378841#M95255</link>
    <description>&lt;P&gt;ah yes, you're not using the same fields in your &lt;CODE&gt;stats&lt;/CODE&gt; and &lt;CODE&gt;eventstats&lt;/CODE&gt;, make sure you align your field names and use the ones from your logs for tran_time_ms, action and the rest ^^&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 00:38:34 GMT</pubDate>
    <dc:creator>DavidHourani</dc:creator>
    <dc:date>2020-09-30T00:38:34Z</dc:date>
    <item>
      <title>Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378832#M95246</link>
      <description>&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/746994/trend-scenario-three-dimensional-data.html#comment-747409"&gt;https://answers.splunk.com/answers/746994/trend-scenario-three-dimensional-data.html#comment-747409&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Extending this problem ...I want to show only those results (pages\action combo) for which daily average processing time has worsen the most... let's say by 10 % ... or to make it simple ... top 10 worst performing results (pages\action combo) since the start of time range .. example .. comparing today with 7th day before [last 7 days]..&lt;BR /&gt;
this is really complex...&lt;/P&gt;</description>
      <pubDate>Sun, 19 May 2019 16:26:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378832#M95246</guid>
      <dc:creator>reverse</dc:creator>
      <dc:date>2019-05-19T16:26:34Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378833#M95247</link>
      <description>&lt;P&gt;you mean you want to compare this Monday with last Monday and so on?&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 00:14:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378833#M95247</guid>
      <dc:creator>nabeel652</dc:creator>
      <dc:date>2019-05-20T00:14:30Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378834#M95248</link>
      <description>&lt;P&gt;yo got it .. whatever is the date range .. last day -first day and worse 10&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 00:25:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378834#M95248</guid>
      <dc:creator>reverse</dc:creator>
      <dc:date>2019-05-20T00:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378835#M95249</link>
      <description>&lt;P&gt;You can modify this code according to your requirements:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| eval day_of_week=strftime(_time,"%w")  | stats sum(count) as sum by day_of_week _time | sort by day_of_week | streamstats last(sum) as lastSum  current=false window=1 | where isnotnull(lastSum) | eval change = (sum-lastSum)/lastSum*100 | where change&amp;gt;15
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 20 May 2019 01:06:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378835#M95249</guid>
      <dc:creator>nabeel652</dc:creator>
      <dc:date>2019-05-20T01:06:01Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378836#M95250</link>
      <description>&lt;P&gt;day_of_week is 0-6 (Sunday-Saturday)&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:36:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378836#M95250</guid>
      <dc:creator>nabeel652</dc:creator>
      <dc:date>2020-09-30T00:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378837#M95251</link>
      <description>&lt;P&gt;do you always have values for your pages ? Because in this case if it's a new page with bad performance it won't show at all.&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 06:02:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378837#M95251</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-05-20T06:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378838#M95252</link>
      <description>&lt;P&gt;Hi again @reverse,&lt;/P&gt;

&lt;P&gt;So starting with this from the previous question :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; ... |bucket span=1h _time | stats avg(processing_time) as average_processing_time by page_id ,action_id,_time
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You have to add this :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| eval week_day=strftime(_time,"%w") 
| eventstats avg(average_processing_time) as average_trend by week_day, page_id ,action_id
| eval processing_time_change=(average_processing_time/average_trend)*100 
| where processing_time_change&amp;gt;10 
| sort 10 -processing_time_change
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will first build an avg for a specific results over the same day of the previous weeks. Then calculate the current change in processing time compared to the overall average. Then give you the top 10 biggest changes.&lt;/P&gt;

&lt;P&gt;Cheers,&lt;BR /&gt;
David&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 06:16:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378838#M95252</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-05-20T06:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378839#M95253</link>
      <description>&lt;P&gt;it says - "No results found."&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 18:45:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378839#M95253</guid>
      <dc:creator>reverse</dc:creator>
      <dc:date>2019-05-20T18:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378840#M95254</link>
      <description>&lt;P&gt;no results after eventstats&lt;/P&gt;

&lt;P&gt;|bucket span=1d _time | stats avg(tran_time_ms) by page_id ,action,_time| eval week_day=strftime(_time,"%w") &lt;BR /&gt;
 | eventstats avg(average_processing_time) as average_trend by week_day, page_id ,action_id&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:37:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378840#M95254</guid>
      <dc:creator>reverse</dc:creator>
      <dc:date>2020-09-30T00:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: Trend scenario II- three dimensional data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378841#M95255</link>
      <description>&lt;P&gt;ah yes, you're not using the same fields in your &lt;CODE&gt;stats&lt;/CODE&gt; and &lt;CODE&gt;eventstats&lt;/CODE&gt;, make sure you align your field names and use the ones from your logs for tran_time_ms, action and the rest ^^&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:38:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Trend-scenario-II-three-dimensional-data/m-p/378841#M95255</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2020-09-30T00:38:34Z</dc:date>
    </item>
  </channel>
</rss>

