Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
check_filemaker
1.0
2010-10-17
- Nagios 2.x
- Nagios 3.x
GPL
93930
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!
#Required: php cli with cURL extension. Filemaker API(included),FM Web Publishing configured correctly.
#Quick Description: This script uses the FileMaker PHP API to run a listLayouts() query a server database.
#Why?: Sometimes a check_ping or check_service doesn't tell you enough.
If your FM Database Server gets hosed and people cannot connect to the databases these checks will never notify you.
#Detailed Description: Uses a provided Database, Hostname, Username, and Password as arguments.
They then get passed to the PHP command line as "php check_filemaker.php -d $ARG1$ -h HOSTNAME -u $USER2$ -p $USER3".
#What: Nagios check_filemaker.php plugin
#Intended For: Filemaker developers who want to monitor their clients' databases using Nagios.
#Required: php cli with cURL extension. Filemaker API (included),FM Web Publishing configured correctly.
#Quick Description: This script uses the FileMaker PHP API to run a listLayouts() query a server database.
#Why?: Sometimes a check_ping or check_service doesn't tell you enough.
If your FM Database Server gets hosed and people cannot connect to the databases these checks will never notify you.
#Detailed Description: Uses a provided Database, Hostname, Username, and Password as arguments.
They then get passed to the PHP command line as "php check_filemaker.php -d $ARG1$ -h HOSTNAME -u $USER2$ -p $USER3".
The best way to implement this script is to have a generic username and password.
1.
EDIT: /usr/local/nagios/etc/resource.cfg (add them here so the whole world doesn't see them)
ADD: macros for username and password ($USER1$ is already used for libexec path)
$USER2$=HiMyNameIs
$USER3$=SecretWord
***read the resource.cfg file and dont be an idiot and try to change the macros to something else.
2.
EDIT:/usr/local/nagios/etc/objects/commands.cfg
ADD: check_command
# 'check_filemaker' command definition
define command {
command_name check_filemaker
command_line $USER1$/check_filemaker.php -d $ARG1$ -H $HOSTADDRESS$ -u $USER2$ -p $USER3$
}
3.
EDIT: your host definition config file
ADD: service definition
#'check_filemaker service'
define service{
use generic-service
host_name clients-fmserver
service_description FileMaker DB Connection
check_command check_filemaker!DataBase
}
***Obviously change DataBase to whatever your database name is that your connecting to.
4. tar zxvf check_filemaker.tar.gz to /usr/local/nagios/libexec/ directory
change ownership of files to nagios user
chown nagios:nagios /user/local/nagios/libexec/check_filemaker.php FileMaker.php
chown -R nagios:nagios /user/local/libexec/FileMaker
make check_filemaker.php executable
chmod 744 /user/local/nagios/libexec/check_filemaker.php
*/
#Intended For: Filemaker developers who want to monitor their clients' databases using Nagios.
#Required: php cli with cURL extension. Filemaker API (included),FM Web Publishing configured correctly.
#Quick Description: This script uses the FileMaker PHP API to run a listLayouts() query a server database.
#Why?: Sometimes a check_ping or check_service doesn't tell you enough.
If your FM Database Server gets hosed and people cannot connect to the databases these checks will never notify you.
#Detailed Description: Uses a provided Database, Hostname, Username, and Password as arguments.
They then get passed to the PHP command line as "php check_filemaker.php -d $ARG1$ -h HOSTNAME -u $USER2$ -p $USER3".
The best way to implement this script is to have a generic username and password.
1.
EDIT: /usr/local/nagios/etc/resource.cfg (add them here so the whole world doesn't see them)
ADD: macros for username and password ($USER1$ is already used for libexec path)
$USER2$=HiMyNameIs
$USER3$=SecretWord
***read the resource.cfg file and dont be an idiot and try to change the macros to something else.
2.
EDIT:/usr/local/nagios/etc/objects/commands.cfg
ADD: check_command
# 'check_filemaker' command definition
define command {
command_name check_filemaker
command_line $USER1$/check_filemaker.php -d $ARG1$ -H $HOSTADDRESS$ -u $USER2$ -p $USER3$
}
3.
EDIT: your host definition config file
ADD: service definition
#'check_filemaker service'
define service{
use generic-service
host_name clients-fmserver
service_description FileMaker DB Connection
check_command check_filemaker!DataBase
}
***Obviously change DataBase to whatever your database name is that your connecting to.
4. tar zxvf check_filemaker.tar.gz to /usr/local/nagios/libexec/ directory
change ownership of files to nagios user
chown nagios:nagios /user/local/nagios/libexec/check_filemaker.php FileMaker.php
chown -R nagios:nagios /user/local/libexec/FileMaker
make check_filemaker.php executable
chmod 744 /user/local/nagios/libexec/check_filemaker.php
*/
Reviews (0)
Be the first to review this listing!