Page 1 of 2

URL transactional moniotoring

Posted: Wed Mar 12, 2014 8:24 am
by ravish78
Team,

We are performing URL transactional moniotroing.We have downloaded webinject from CPAN ad it is working fine when checked manually with our script but
when we checked using webtransactional wizard it is not working.This might be due to old version in nagios.

What is the process to upgrade webinject in nagios.Do we need to submit a ticket?

Re: URL transactional moniotoring

Posted: Wed Mar 12, 2014 10:28 am
by slansing
Could we see the output that the web interface is giving you once the check is configured, and also what is being output when manually run from the command line?

Re: URL transactional moniotoring

Posted: Thu Mar 13, 2014 10:08 am
by ravish78
Our test cases require the advanced config options in version 1.86 (current CPAN) for redirects and authentication. Current errors are immediate failures of test case and “out of bounds” errors on the return code from webinject.pl

Re: URL transactional moniotoring

Posted: Thu Mar 13, 2014 10:54 am
by abrist
Can you post the full commands and check configurations that you are using?

Re: URL transactional moniotoring

Posted: Thu Mar 13, 2014 11:13 am
by Jaysen.ODell
This was written for webinspect 1.86 (CPAN) to be implemented in XI...

This follows our SSO solution which creates dynamic redirects. We want to simulate a user click trail to ensure that we are monitoring for the real end user trail, not an artificially accurate trail. The error seems to be in the max_redirect directive (added in 1.5) and the auth/cookie enhancements made in 1.6.

cfg file contents:

Code: Select all

<testcasefile>nagios-test.xml</testcasefile>
<globalhttplog>yes</globalhttplog>
<max_redirect>5</max_redirect>
test case file contents:

Code: Select all

<testcases repeat="1">
<case
        id="1"
        desctiption1="Nagios login test"
        desctiption2="Go to homepage and follow redirect to S3"
        url="http://nagios.corp.xerox.com"
        verifypositive="Title: S3 Application Login"
/>

<case
        id="2"
        desctiption1="Nagios login test"
        desctiption2="Provide S3 credentials and follow redirec to Nagios"
        method="post"
        posttype="application/x-www-form-urlencoded"
        postbody="USER=removed&PASSWORD=removed|&target=http://nagios.corp.xerox.com/nagiosxi"
        url="https://xww.s3.world.xerox.com/dmt2/login/login.fcc"
        verifypostive="Title: Nagios XI"
/>

</testcases>

Re: URL transactional moniotoring

Posted: Thu Mar 13, 2014 11:19 am
by Jaysen.ODell
Forgot to add that putting the test case into a XI webinject config fails. test cases supplied to XI via web transaction wizard.

Moderator note: Both posters are from the same organization, do not split topic.

Re: URL transactional moniotoring

Posted: Thu Mar 13, 2014 5:11 pm
by tmcdonald
What error does it show in the XI interface? Like if you go to Service Detail on the Home page and find the service, what is in the Status Information field? A screenshot would be nice.

Re: URL transactional moniotoring

Posted: Tue Mar 25, 2014 12:51 pm
by Jaysen.ODell
tmcdonald wrote:What error does it show in the XI interface? Like if you go to Service Detail on the Home page and find the service, what is in the Status Information field? A screenshot would be nice.
Sorry for the delay. As you may be aware we have had some issues with os upgrades that are taking precedent. I will need to recreate the script and test. I'll try to get screen shot by end of the week.

Re: URL transactional moniotoring

Posted: Tue Mar 25, 2014 2:26 pm
by lmiltchev
Sounds good. Post the screenshot whenever you are ready.

Re: URL transactional moniotoring

Posted: Thu Mar 27, 2014 10:46 am
by Jaysen.ODell
attached. the core lists the same error.

OS level is failing on a 301 and the verify positive. the failure is simple to explain: You have to follow the 301 (which is dynamic) to get the expected string. But since the nagios webinject is 1.4 it will not follow redirects. Also, since I can't actually edit the parent config (the monitoring wizard hides that), I can't enable the max_redirect variable used for >1.5 versions to allow following the 301.