All Apps and Add-ons

Example of how to predict web traffic volume?

sloshburch
Splunk Employee
Splunk Employee

Does anyone have examples of how to use Splunk to predict web traffic volume?

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 on this and other examples, download the free Splunk Essentials for Infrastructure Troubleshooting and Monitoring app on Splunkbase.

Application support teams can get a snapshot of the volume of traffic on web servers to forecast spikes and future growth. Use the web access log files in the Splunk platform to calculate the total number of times the web server farm is accessed at a given time. Apply the Splunk platform's machine learning tools to forecast traffic based on the historical trends.

Load data

How to implement: This example use case depends on web server log data.

Respective to your enviroment, install the Splunk Add-on for Apache Web Server and the Splunk Add-on for Microsoft IIS. Find the Splunk Add-on for Apache Web Server and the Splunk Add-on for Microsoft IIS on Splunkbase.

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.

Data check: Run the following search to verify you are searching for normalized web data that is ready for this use case:

earliest=-1day index=* tag=web
| head 10

Get insights

Predict the web traffic volume of your web applications based on the actual volume of traffic.

Run the following search.

index=* tag=web
| timechart count AS Hits
| predict future_timespan=30 Hits AS "Projected Hits"

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

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 on this and other examples, download the free Splunk Essentials for Infrastructure Troubleshooting and Monitoring app on Splunkbase.

Application support teams can get a snapshot of the volume of traffic on web servers to forecast spikes and future growth. Use the web access log files in the Splunk platform to calculate the total number of times the web server farm is accessed at a given time. Apply the Splunk platform's machine learning tools to forecast traffic based on the historical trends.

Load data

How to implement: This example use case depends on web server log data.

Respective to your enviroment, install the Splunk Add-on for Apache Web Server and the Splunk Add-on for Microsoft IIS. Find the Splunk Add-on for Apache Web Server and the Splunk Add-on for Microsoft IIS on Splunkbase.

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.

Data check: Run the following search to verify you are searching for normalized web data that is ready for this use case:

earliest=-1day index=* tag=web
| head 10

Get insights

Predict the web traffic volume of your web applications based on the actual volume of traffic.

Run the following search.

index=* tag=web
| timechart count AS Hits
| predict future_timespan=30 Hits AS "Projected Hits"

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

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 ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...