Home Directory Addons Active Checks Splunk Forwarder Mangement Client check

Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

Directory Tree

Splunk Forwarder Mangement Client check

Current Version
1.0
Last Release Date
2015-02-20
Compatible With
  • Nagios 3.x
  • Nagios 4.x
Owner
License
GPL
Hits
11455
Files:
FileDescription
check-licenseusage.zipcheck-licenseusage.zip
Nagios CSP

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Monitoring Made Magically Better

  • Nagios Core on Overdrive
  • Powerful Monitoring Dashboards
  • Time-Saving Configuration Wizards
  • Open Source Powered Monitoring On Steroids
  • And So Much More!
The Nagios plugin ensures that all your clients (Indexers, Search Heads, Forwarders) are running at least the defined Splunk version. Otherwise an error will be generated.
The Nagios plugin ensures that all your clients (Indexers, Search Heads, Forwarders) are running at least the defined Splunk version. Otherwise an error will be generated.

You need to have Forwarder Management implemented for this check. On the client you just need to point it to one Forwarder Management server, which can be any Splunk server in your environment.
You can set the Forwarder to the Forwarder Management server with the command

$SPLUNK_HOME$/bin/splunk set deploy-poll bd20.bwlab.loc:8089

Parameters:
-servername
the servername or ip address of the Deployment Server / Forwarder Mangement to be checked - default localhost

-port
port of splunkd - default 8089

-protocol
protocol to use to communicate with splund - default: https

-timeout
connectiontimeout to slunkd in milliseconds - default 5000

-username
username to use to login to splunkd

-password
password to use with splunkd

-minbuild
buildversion of client to check. have to be passed as an integer value if client runs on a lower buildlevel a critial message will be generated
example build numbers
version 4.3.3 = build 128297
version 6.0.2 = build 196940
version 6.1.1 = build 207789
version 6.1.3 = build 220630
version 6.1.4 = build 233537
version 6.1.5 = build 239630
version 6.2.0 = build 237341
version 6.2.1 = build 245427