<?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: Example of how to identify slow web pages? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-identify-slow-web-pages/m-p/474771#M58346</link>
    <description>&lt;P&gt;&lt;EM&gt;The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the &lt;A href="https://docs.splunk.com/Documentation/UseCases" target="_blank"&gt;Splunk Platform Use Cases&lt;/A&gt; manual.&lt;/EM&gt;&lt;/P&gt;

&lt;H2&gt;&lt;EM&gt;For more information on this and other examples, download the free &lt;A href="https://splunkbase.splunk.com/app/4091" target="_blank"&gt;Splunk Essentials for Infrastructure Troubleshooting and Monitoring&lt;/A&gt; app on Splunkbase.&lt;/EM&gt;&lt;/H2&gt;

&lt;P&gt;Application developers can use web server access logs to summarize the response times of each page and identify the worst performing pages so that development teams can improve application performance.&lt;/P&gt;

&lt;H1&gt;Load data&lt;/H1&gt;

&lt;P&gt;&lt;STRONG&gt;How to implement:&lt;/STRONG&gt; This example use case depends on data from web server logs.&lt;/P&gt;

&lt;P&gt;Install the Splunk Add-on for Apache Web Server or the Splunk Add-on for Microsoft IIS. Follow the documentation to learn how to install these add-ons, configure the web server to record the &lt;CODE&gt;response_time&lt;/CODE&gt; in the raw data, and make the &lt;CODE&gt;response_time&lt;/CODE&gt; field available at search time. Find the &lt;A href="https://splunkbase.splunk.com/app/3186/" target="_blank"&gt;Splunk Add-on for Apache Web Server&lt;/A&gt; and the &lt;A href="https://splunkbase.splunk.com/app/3185/" target="_blank"&gt;Splunk Add-on for Microsoft IIS&lt;/A&gt; on Splunkbase.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Data check:&lt;/STRONG&gt; Run the following search to verify you are searching for normalized &lt;A href="https://docs.splunk.com/Documentation/CIM/latest/User/Web" target="_blank"&gt;web&lt;/A&gt; data that is ready for this use case: &lt;PRE&gt;earliest=-1day index=* tag=web&lt;BR /&gt;
| head 10&lt;/PRE&gt;&lt;/P&gt;

&lt;H1&gt;Get insights&lt;/H1&gt;

&lt;P&gt;Use web server logs to gather web-page response times to identify whether application performance may cause a negative end-user experience.&lt;/P&gt;

&lt;P&gt;Run the following search.&lt;BR /&gt;
&lt;PRE&gt;index=* tag=web&lt;BR /&gt;
| stats avg(response_time) AS art BY uri_path&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; In searches, replace the asterisk in &lt;CODE&gt;index=*&lt;/CODE&gt; with the name of the &lt;A href="https://docs.splunk.com/Splexicon:Index" target="_blank"&gt;index&lt;/A&gt; that contains the data. By default, Splunk stores data in the &lt;CODE&gt;main&lt;/CODE&gt; index. Therefore, &lt;CODE&gt;index=*&lt;/CODE&gt; becomes &lt;CODE&gt;index=main&lt;/CODE&gt;. Use the &lt;CODE&gt;OR&lt;/CODE&gt; operator to &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Search/Searchindexes#Specify_one_or_multiple_indexes_to_search" target="_blank"&gt;specify one or multiple indexes to search&lt;/A&gt;. For example, &lt;CODE&gt;index=main OR index=security&lt;/CODE&gt;. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Aboutmanagingindexes" target="_blank"&gt;About managing indexes&lt;/A&gt; and &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Howindexingworks" target="_blank"&gt;How indexing works&lt;/A&gt; in Splunk docs for details.&lt;/P&gt;

&lt;H1&gt;Help&lt;/H1&gt;

&lt;P&gt;See the following video for more details related to this use case.&lt;BR /&gt;
&lt;A href="https://www.youtube.com/watch?v=TkjSeSClYaQ&amp;amp;list=PL7zWAA-DF0k98jw_Hseh7JyQ74fq8AxYT" target="_blank"&gt;&lt;IMG alt="identify slow web pages" src="https://i.ytimg.com/vi/TkjSeSClYaQ/hqdefault.jpg" /&gt;&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If no results appear, it may be because the add-ons were not deployed to the search heads, so the needed tags and fields are not defined. Deploy the add-ons to the search heads to access the needed tags and fields. See &lt;A href="https://docs.splunk.com/Documentation/AddOns/released/Overview/Installingadd-ons" target="_blank"&gt;About installing Splunk add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For troubleshooting tips that you can apply to all add-ons, see &lt;A href="http://docs.splunk.com/Documentation/AddOns/released/Overview/Troubleshootadd-ons" target="_blank"&gt;Troubleshoot add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For more support, &lt;A href="https://answers.splunk.com/answers/ask.html?topics=usecase" target="_blank"&gt;post a question to the Splunk Answers community&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 03:30:59 GMT</pubDate>
    <dc:creator>sloshburch</dc:creator>
    <dc:date>2020-09-30T03:30:59Z</dc:date>
    <item>
      <title>Example of how to identify slow web pages?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-identify-slow-web-pages/m-p/474770#M58345</link>
      <description>&lt;P&gt;Does anyone have examples of how to use Splunk to identify slow web pages?&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jan 2020 18:09:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-identify-slow-web-pages/m-p/474770#M58345</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-01-03T18:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: Example of how to identify slow web pages?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-identify-slow-web-pages/m-p/474771#M58346</link>
      <description>&lt;P&gt;&lt;EM&gt;The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the &lt;A href="https://docs.splunk.com/Documentation/UseCases" target="_blank"&gt;Splunk Platform Use Cases&lt;/A&gt; manual.&lt;/EM&gt;&lt;/P&gt;

&lt;H2&gt;&lt;EM&gt;For more information on this and other examples, download the free &lt;A href="https://splunkbase.splunk.com/app/4091" target="_blank"&gt;Splunk Essentials for Infrastructure Troubleshooting and Monitoring&lt;/A&gt; app on Splunkbase.&lt;/EM&gt;&lt;/H2&gt;

&lt;P&gt;Application developers can use web server access logs to summarize the response times of each page and identify the worst performing pages so that development teams can improve application performance.&lt;/P&gt;

&lt;H1&gt;Load data&lt;/H1&gt;

&lt;P&gt;&lt;STRONG&gt;How to implement:&lt;/STRONG&gt; This example use case depends on data from web server logs.&lt;/P&gt;

&lt;P&gt;Install the Splunk Add-on for Apache Web Server or the Splunk Add-on for Microsoft IIS. Follow the documentation to learn how to install these add-ons, configure the web server to record the &lt;CODE&gt;response_time&lt;/CODE&gt; in the raw data, and make the &lt;CODE&gt;response_time&lt;/CODE&gt; field available at search time. Find the &lt;A href="https://splunkbase.splunk.com/app/3186/" target="_blank"&gt;Splunk Add-on for Apache Web Server&lt;/A&gt; and the &lt;A href="https://splunkbase.splunk.com/app/3185/" target="_blank"&gt;Splunk Add-on for Microsoft IIS&lt;/A&gt; on Splunkbase.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Data check:&lt;/STRONG&gt; Run the following search to verify you are searching for normalized &lt;A href="https://docs.splunk.com/Documentation/CIM/latest/User/Web" target="_blank"&gt;web&lt;/A&gt; data that is ready for this use case: &lt;PRE&gt;earliest=-1day index=* tag=web&lt;BR /&gt;
| head 10&lt;/PRE&gt;&lt;/P&gt;

&lt;H1&gt;Get insights&lt;/H1&gt;

&lt;P&gt;Use web server logs to gather web-page response times to identify whether application performance may cause a negative end-user experience.&lt;/P&gt;

&lt;P&gt;Run the following search.&lt;BR /&gt;
&lt;PRE&gt;index=* tag=web&lt;BR /&gt;
| stats avg(response_time) AS art BY uri_path&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; In searches, replace the asterisk in &lt;CODE&gt;index=*&lt;/CODE&gt; with the name of the &lt;A href="https://docs.splunk.com/Splexicon:Index" target="_blank"&gt;index&lt;/A&gt; that contains the data. By default, Splunk stores data in the &lt;CODE&gt;main&lt;/CODE&gt; index. Therefore, &lt;CODE&gt;index=*&lt;/CODE&gt; becomes &lt;CODE&gt;index=main&lt;/CODE&gt;. Use the &lt;CODE&gt;OR&lt;/CODE&gt; operator to &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Search/Searchindexes#Specify_one_or_multiple_indexes_to_search" target="_blank"&gt;specify one or multiple indexes to search&lt;/A&gt;. For example, &lt;CODE&gt;index=main OR index=security&lt;/CODE&gt;. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Aboutmanagingindexes" target="_blank"&gt;About managing indexes&lt;/A&gt; and &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Howindexingworks" target="_blank"&gt;How indexing works&lt;/A&gt; in Splunk docs for details.&lt;/P&gt;

&lt;H1&gt;Help&lt;/H1&gt;

&lt;P&gt;See the following video for more details related to this use case.&lt;BR /&gt;
&lt;A href="https://www.youtube.com/watch?v=TkjSeSClYaQ&amp;amp;list=PL7zWAA-DF0k98jw_Hseh7JyQ74fq8AxYT" target="_blank"&gt;&lt;IMG alt="identify slow web pages" src="https://i.ytimg.com/vi/TkjSeSClYaQ/hqdefault.jpg" /&gt;&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;If no results appear, it may be because the add-ons were not deployed to the search heads, so the needed tags and fields are not defined. Deploy the add-ons to the search heads to access the needed tags and fields. See &lt;A href="https://docs.splunk.com/Documentation/AddOns/released/Overview/Installingadd-ons" target="_blank"&gt;About installing Splunk add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For troubleshooting tips that you can apply to all add-ons, see &lt;A href="http://docs.splunk.com/Documentation/AddOns/released/Overview/Troubleshootadd-ons" target="_blank"&gt;Troubleshoot add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For more support, &lt;A href="https://answers.splunk.com/answers/ask.html?topics=usecase" target="_blank"&gt;post a question to the Splunk Answers community&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 03:30:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-identify-slow-web-pages/m-p/474771#M58346</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-09-30T03:30:59Z</dc:date>
    </item>
  </channel>
</rss>

