Checking OWA
p1 at fhri.org
p1 at fhri.org
Mon Jun 15 18:35:06 CEST 2009
Very cool, thanks Jon for pointing me in the right direction.
I'm now actually able to drill down all the way to an individual message
and check for content:
check_http -H ExchServ1 --ssl -a "dom1\nagios":NagiosPass1 -u
/exchange/nagios/Inbox/Nagios%20OWA%20content%20check%20-%20DO%20NOT%20D
ELETE.EML?Cmd=open -s "monitor OWA functionality"
Exactly what I wanted and then some :)
--
Paul
-----Original Message-----
From: Jon Angliss [mailto:jon at netdork.net]
Sent: Friday, June 12, 2009 5:27 PM
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Checking OWA
On Fri, 12 Jun 2009 11:43:29 -0700, <p1 at fhri.org> wrote:
>Trying to use check_http to monitor OWA. I can monitor the site's
>response, SSL and even login, but not content, which would be a truly
>thorough test I used to be able to do some time back. Getting stuck
>with this error, seen in verbose output from the plugin:
>
>This page uses frames, but your browser doesn't support them.
That's exactly what I'd expect to see when you don't actually request
the page with content, and just call the main frameset page.
>
>I see the same error if I disable frame support in Firefox. Anyone
else
>monitoring OWA content?
What content are you actually looking for? Is there a specific email
you're looking for? If so, you don't want to call /exchange/nagios,
you want to look for the INBOX instead. If you view the source of the
frameset page, you will see two frame calls, the body looks something
like this:
<FRAMESET>
<FRAME name="navbar" src="./?Cmd=navbar">
<FRAME name="viewer" src="Inbox/?Cmd=contents">
<NOFRAMES>
<BODY><P>This page uses frames, but your browser doesn't support
them.</P></BODY>
</NOFRAMES>
</FRAMESET>
Note, I have trimmed the code to make it actually readable. You can
see the navigation bar, and the inbox calls. So your nagios
check_http call should in fact look like this:
./check_http -H exchange -u "/exchange/nagios/Inbox/?Cmd=contents" -a
"dom1\nagios":nagiospass1 -s "...."
Another note, you'll find the code for {name} : INBOX is split by HTML
code, so your check needs to account for it. In my case, the check
would be:
-s 'Jonathan Angliss</B></FONT></A></FONT......'
If you're just looking for the name resolution, just use that instead.
I just did a quick test to validate, and it looks like the following
page is expecting session data, so you might end up having to string
together a number of tests using cURL, or using webinject to login,
and access the page.
--
Jonathan Angliss
<jon at netdork.net>
------------------------------------------------------------------------
------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
ea926p
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list