Does anyone have examples of how to use Splunk to monitor application network usage?
The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the Splunk Platform Use Cases manual.
Network administrators can monitor the amount of network traffic being generated by web applications so you can forecast future volumes as your application portfolio grows.
How to implement: This example use case depends on web server logs.
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. 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
Leverage the bandwidth utilization details from your web access logs to track past usage and predict future bandwidth utilization using the predict
machine learning command.
Run the following search.
index=* tag=web
| timechart sum(bytes) AS "Actual Bytes Sent"
| predict future_timespan=30 "Actual Bytes Sent" AS "Predicted Use"
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.
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.
The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the Splunk Platform Use Cases manual.
Network administrators can monitor the amount of network traffic being generated by web applications so you can forecast future volumes as your application portfolio grows.
How to implement: This example use case depends on web server logs.
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. 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
Leverage the bandwidth utilization details from your web access logs to track past usage and predict future bandwidth utilization using the predict
machine learning command.
Run the following search.
index=* tag=web
| timechart sum(bytes) AS "Actual Bytes Sent"
| predict future_timespan=30 "Actual Bytes Sent" AS "Predicted Use"
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.
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.