Example of how to measure application error rate?

sloshburch — Tue, 28 Jan 2020 20:29:50 GMT

Does anyone have examples of how to use Splunk to measure application error rate?

Re: Example of how to measure application error rate?

sloshburch — Wed, 30 Sep 2020 03:50:08 GMT

The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the Splunk Platform Use Cases manual.

For more information about this example see KPIs and thresholds for the ITSI APM Module in the Splunk ITSI Module for Application Performance Monitoring* manual.*

Application support engineers need proactive and predictive monitoring in their applications environments to trend past performance and predict future things like application response times, error rates, end user experiences to reduce the time to resolution for application issues. Set up this example use case to measure application error rate in your environment.

Load data

How to implement: This example use case depends on event data from application performance monitoring platforms.

Install the appropriate add-ons for the platforms that exist in your environment.

You can find installation and configuration instructions in the Details tab of each Splunkbase item. Additional configuration details are available in the ITSI Module for Application Performance Monitoring section in the Install and Configure the Splunk ITSI Module for Application Performance Monitoring manual.

Best practice: For more granular results with scripted inputs, you can increase the frequency at which the input runs using the interval setting in inputs.conf. Running the input more frequently consumes more storage, and running it less frequently uses less, which can affect license consumption. The default interval is 60 seconds. See Scripted Input in the input.conf topic of the Splunk Enterprise Admin manual.

Best practice: For all of the data inputs, specify a desired target index to provide a more sustainable practice for data access controls and retention models. By default, Splunk collects the data in the default index named main.

Get insights

Run the following search.

index=* tag=application tag=performance tag=apm app_title=* 

| timechart span=5min avg(error_rate) BY host

Best practice: In searches, replace the asterisk in index=* with the name of the index that contains the data. By default, Splunk stores data in the main index. Therefore, index=* becomes index=main. Use the OR operator to specify one or multiple indexes to search. For example, index=main OR index=security. See About managing indexes and How indexing works in Splunk docs for details.

Help

The Troubleshoot the ITSI APM Module section in the Install and Configure the Splunk ITSI Module for Application Performance Monitoring manual lists troubleshooting resources you can apply to this example use case.

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 About installing Splunk add-ons in the Splunk Add-ons manual.

For troubleshooting tips that you can apply to all add-ons, see Troubleshoot add-ons in the Splunk Add-ons manual.

For more support, post a question to the Splunk Answers community.