Splunk® Deployment Monitor App (Legacy)

Deploy and Use Splunk Deployment Monitor App

Download manual as PDF

Download topic as PDF

Other deployment considerations

This topic covers important considerations you should review and understand before proceeding with a production Splunk deployment.

Storage considerations

The Deployment Monitor requires a small amount of additional storage to accommodate the report acceleration summaries that it creates from existing data.

To determine the size of the report acceleration summaries created by the Deployment Monitor, use Splunk Manager:

1. Go to Manager > Report Acceleration Summaries. You will see four report summaries created by the Deployment Monitor:

  • indexers_summary_10m
  • forwarders_summary_10m
  • sourcetypes_summary_10m
  • pools_summary_10m

2. Click on the Summary ID for each summary. The Size on Disk field tells you how much space the summary uses.

See the topic "Manage report acceleration" in the Knowledge Manager Manual for information on how report acceleration summaries are stored.

Licensing information

The Deployment Monitor doesn't index any new data, so it does not have an impact on your licensing volume.

Last modified on 24 October, 2012
PREVIOUS
Where to install
  NEXT
Install the Deployment Monitor

This documentation applies to the following versions of Splunk® Deployment Monitor App (Legacy): 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters