<?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 Example of how to track application errors? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-track-application-errors/m-p/492217#M60595</link>
    <description>&lt;P&gt;Does anyone have examples of how to use Splunk to track application errors?     &lt;/P&gt;</description>
    <pubDate>Tue, 28 Jan 2020 16:37:35 GMT</pubDate>
    <dc:creator>sloshburch</dc:creator>
    <dc:date>2020-01-28T16:37:35Z</dc:date>
    <item>
      <title>Example of how to track application errors?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-track-application-errors/m-p/492217#M60595</link>
      <description>&lt;P&gt;Does anyone have examples of how to use Splunk to track application errors?     &lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2020 16:37:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-track-application-errors/m-p/492217#M60595</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-01-28T16:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Example of how to track application errors?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-track-application-errors/m-p/492218#M60596</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"&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"&gt;Splunk Essentials for Infrastructure Troubleshooting and Monitoring&lt;/A&gt; app on Splunkbase.&lt;/EM&gt;&lt;/H2&gt;

&lt;P&gt;Application development teams need know where their applications experience errors to fix the issue and provide a better user experience. Add web access logs to the Splunk platform to gain valuable insights on page access, including the HTTP response codes. Analyze the response codes and their frequency to identify potential areas for improvement in applications.&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 access and error logs.&lt;/P&gt;

&lt;P&gt;Install the Splunk Add-on for Apache Web Server or the Splunk Add-on for Microsoft IIS. Find the &lt;A href="https://splunkbase.splunk.com/app/3186/"&gt;Splunk Add-on for Apache Web Server&lt;/A&gt; and the &lt;A href="https://splunkbase.splunk.com/app/3185/"&gt;Splunk Add-on for Microsoft IIS&lt;/A&gt; on Splunkbase. You can find installation and configuration instructions in the &lt;STRONG&gt;Details&lt;/STRONG&gt; tab of each Splunkbase item.&lt;/P&gt;

&lt;P&gt;Run the following search to verify you are searching for normalized &lt;A href="https://docs.splunk.com/Documentation/CIM/latest/User/Web"&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;To identify where errors are originating from, run the following search.&lt;BR /&gt;
&lt;PRE&gt;index=* tag=web status&amp;gt;=400 &lt;BR /&gt;
| stats count BY uri_path, status &lt;BR /&gt;
| sort limit=20 -count&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"&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"&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"&gt;About managing indexes&lt;/A&gt; and &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Howindexingworks"&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;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"&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"&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"&gt;post a question to the Splunk Answers community&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2020 16:37:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Example-of-how-to-track-application-errors/m-p/492218#M60596</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-01-28T16:37:49Z</dc:date>
    </item>
  </channel>
</rss>

