spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

WebInject Scripting to Perform Advanced Monitoring

Written by SPK Blog Post
Published on August 19, 2011

Nagios is a wonderful tool. However, there are limits to what you can do with it directly. As my colleague Brad discussed in a recent blog post, using NRPE is a powerful tool for Windows. For complicated web checks that require multi-step operation, we use: WebInject.

WebInject enhances Nagios in multiple ways:

1) Creates stateful requests by defining variables
2) Allows multi-step processing
3) Provides both GET and POST
4) Supports unlimited customization in each step

Each step in the configuration is a “case” with a unique “id”. WebInject also allows for setting variables such as the “SSO_USER” and “SSO_PASS” variable.

Each webinject starts with a configuration file that „s pretty simple. You have to estimate the length of time in seconds. If this “globaltimeout” is reached, then the script will fail so you need to accommodate for busy times on the servers. The “reporttype” needs to be Nagios in order for it to integrate. The “testcasefile” is the filename of the actual request:

To read this full HowTo download: Webinject_Websites

Subscribe to our blog for useful How To documents and industry tech tips related to remote server monitoring, Engineering Applications, software engineering tools and methods, and other topics of interest.

Related Resources

Why Late-Stage Changes Are Killing Your Time to Market

Why Late-Stage Changes Are Killing Your Time to Market

Key Takeaways Late-stage changes get expensive fast: The farther a problem travels through design, testing, and manufacturing, the more time, cost, and rework it creates. Disconnected systems and weak traceability are major causes: When requirements, design, software,...

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

Key takeaways Faster engineering does not always require more headcount: Disconnected systems, manual handoffs, rework, and poor visibility often create more delays than a lack of engineering capacity. A digital thread can eliminate major sources of wasted time:...

The Engineering Digital Thread Playbook

The Engineering Digital Thread Playbook

In many organizations, systems operate independently, creating a large visibility problem. A digital thread addresses this by creating a connected flow of product information across the lifecycle. This playbook explains why engineering visibility matters, and how...