Knowledge Management

Example of how to measure application server 5xx errors counts?

sloshburch
Splunk Employee
Splunk Employee

Does anyone have examples of how to use Splunk to measure the count of 5xx errors on application servers?

Tags (1)
0 Karma
1 Solution

sloshburch
Splunk Employee
Splunk Employee

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 Application Server Module KPIs and thresholds in the Splunk IT Service Intelligence Modules manual.

Set up this example use case to find the total server errors for each application server host.

Load data

How to implement: This example use case depends on application server logs.

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 Application Server Module configurations section in the Splunk IT Service Intelligence Modules 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=appserver tag=performance tag=transactions
| eval 5xx_error=if(status>=500 AND status<600, status, null())
| timechart span=5min count(5xx_error) 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 Application Server Module troubleshooting section in the Splunk IT Service Intelligence Modules 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.

View solution in original post

0 Karma

sloshburch
Splunk Employee
Splunk Employee

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 Application Server Module KPIs and thresholds in the Splunk IT Service Intelligence Modules manual.

Set up this example use case to find the total server errors for each application server host.

Load data

How to implement: This example use case depends on application server logs.

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 Application Server Module configurations section in the Splunk IT Service Intelligence Modules 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=appserver tag=performance tag=transactions
| eval 5xx_error=if(status>=500 AND status<600, status, null())
| timechart span=5min count(5xx_error) 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 Application Server Module troubleshooting section in the Splunk IT Service Intelligence Modules 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.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

Splunk is officially part of Cisco

Revolutionizing how our customers build resilience across their entire digital footprint.   Splunk ...

Splunk APM & RUM | Planned Maintenance March 26 - March 28, 2024

There will be planned maintenance for Splunk APM and RUM between March 26, 2024 and March 28, 2024 as ...