Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Siebel CRM on Windows Monitor
Current Version
2.0
Last Release Date
2011-01-15
Compatible With
- Nagios 3.x
Owner
License
GPL
Hits
96840
Files:
| File | Description |
|---|---|
| SIEBMON.zip | All files in a zip |
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!
Although the regular commercial available monitors are adequate, the cost to monitor Siebel is quiet high.
The scripts can run standalone, but can be started up from any monitoring system that reads the standard out and bases the severity on the exit code.
1. Siebel Enterprise availability
2. Siebel Gateway availability
3. Siebel Component group availability (status of components)
4. Siebel Server availability (status of Siebel servers)
5. Siebel Running Tasks runtime... euh timeout check.
- The scripts use srvrmgr.exe to connect to the Siebel Enterprise. Monitoring output is therefore liable. A simple port check is not 100% fail-proof.
- The full output of the srvrmgr.exe is put into a txt file at each monitor interval.
- The output is logged into log files for further troubleshooting. Entries with issues start with a severity (CRIT, WARN, INFO). Logfiles can be limited in size.
- To avoid too many srvrmgr processes, only 1 srvrmgr process is allowed to run. The check is based on the process name coming from WMI. If srvrmgr.exe runs on the server you want to monitor, use the remote monitor possibility.
- Srvrmgr.exe can be called locally or remotely with the Nagios service account credentials using file share or provided within the scripts.
- Components or servers can be excluded.
- Multiple Enterprises can be monitored using provisioning files.
Since the scripts are generic, the Nagios implementation is not documented but you can figure that one out yourself ;-)
More details in the readme.txt file
