Splunk® Deployment Monitor App (Legacy)

Deploy and Use Splunk Deployment Monitor App

This documentation does not apply to the most recent version of Splunk® Deployment Monitor App (Legacy). For documentation on the most recent version, go to the latest release.

Release notes

This topic contains information on changes incorporated into the latest version of the Splunk Deployment Monitor App.

Change log (what's been fixed)

  • Indexer improperly reported as "overloaded" when it's not. Users can now configure the alerting for overloaded indexers. The search has parameters for fill statistical function to use (median, perc95, etc.) and the queue fill ratio threshold (50%, 95%, etc.). (DEPMON-114)
  • License usage dashboard should use rotated license_usage.log.* for the source, rather than the single file license_usage.log. (DEPMON-116)

Migration notes

  • The migration to 5.0.2 triggers an automatic backfill of all the deployment monitor's report acceleration summaries. This can result in a temporary slowdown while the summaries are being regenerated.
Last modified on 19 September, 2013
View license usage  

This documentation applies to the following versions of Splunk® Deployment Monitor App (Legacy): 5.0.2

Acrobat logo Download manual
Acrobat logo Download this page

Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

Was this topic useful?







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