Home Directory Addons Active Checks Splunk Deployment Server 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 Deployment Server Check

Current Version
1.0
Last Release Date
2015-02-18
Compatible With
  • Nagios 3.x
  • Nagios 4.x
Owner
License
GPL
Hits
9974
Files:
FileDescription
check-deploymentclients.zipcheck-deploymentclients.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!
If you use Forwarder Management (also known as Deployment Server) to configure your infrastructure, you really want to make sure your Clients/Forwarders are up-and-running.

This Powershell Script will check that all clients which logged into Deployment Server are reachable.
If you use Forwarder Management (also known as Deployment Server) to configure your infrastructure, you really want to make sure your Clients/Forwarders are up-and-running.

This Powershell Script will check that all clients which logged into Deployment Server are reachable.

Find more information at https://www.batchworks.de/monitoring-splunk-forwarder-management-clients-using-nagios


Parameters:
-servername
Servername or IP address of the Deployment Server/Forwarder Management

-port
Port of splunkd - default 8089

-protocol
Protocol to use to communicate with splunkd - default: https

-timeout
Connection timeout to splunkd in milliseconds - default 5000

-username
Username to use to login to splunkd

-password
Password to use with splunkd

-warn
time in seconds (default 5) which a client is allowed to overdue before a warning is generated, depends on configured phoneHomeIntervalInSecs (default 60) in client settings

-critical
time in seconds (default 300) which a client is allowed to overdue before a critical is generated, depends on configured phoneHomeIntervalInSecs (default 60) in client settings