Here is the latest package I have tried in the
poller.configuration.xml:
<package name="LinuxAntispam"
remote="false">
<filter>(IPADDR != '0.0.0.0' & (pollerCategory LIKE
"%LinuxAntispam%") & (category == 'Server' | category ==
'Infrastructure'))</filter>
<specific>19.19.19.19</specific>
<include-range
begin="1.1.1.1" end="254.254.254.254"/>
<rrd
step="300">
<rra xmlns="">RRA:AVERAGE:0.5:1:2016</rra>
<rra xmlns="">RRA:AVERAGE:0.5:12:1488</rra>
<rra xmlns="">RRA:AVERAGE:0.5:288:366</rra>
<rra xmlns="">RRA:MAX:0.5:288:366</rra>
<rra xmlns="">RRA:MIN:0.5:288:366</rra>
</rrd>
<service
name="Linux-Anitspam" interval="300000"
user-defined="true" status="on">
<parameter key="retry" value="1"/>
<parameter key="timeout" value="5000"/>
<parameter key="rrd-repository"
value="/opt/opennms/share/rrd/response"/>
<parameter key="ds-name" value="linuxantispam"/>
<parameter key="page-sequence">
<!-- this uses a newly implemented feature of poller-configuration.xml
(it has not yet been added to other daemons like capsd, collected, etc)
this feature allows you to insert xml content inside of the parameter tags
rather than as a string in the value attribute -->
<page-sequence>
<!-- <page
path="http://pmx.sophos.com/as-sdk/2.x-latest/linux/antispam.tgz.md5"
ds-name="linuxantispam" port="80"
successMatch="l" /> -->
<!-- <page path="/opennms/j_spring_security_check"
port="80" method="POST" failureMatch="(?s)Your log-in
attempt failed.*Reason: ([^<]*)" failureMessage="Login in Failed:
${1}" successMatch="Log out"> -->
<!-- First get port 80 so we have a clean success -->
<page scheme="http" path="/" port="80"
successMatch="antispam" />
<!-- RIGHT NOW JUST GET THE LOGIN PAGE -->
<page scheme="http"
virtual-host="pmx.sophos.com"
host="pmx.sophos.com"
path="/as-sdk/2.x-latest/linux/antispam.tgz.md5&j_url=/app/home&j_sc=http"
port="80"
failureMessage="Login
failed: ${1}"
http-version="1.1"
successMatch="success" />
<!--timeout="10000" http-version="1.1"-->
<page scheme="http"
virtual-host="pmx.sophos.com"
host="pmx.sophos.com"
path="/as-sdk/2.x-latest/linux/antispam.tgz.md5&j_url=/app/home&j_sc=http"
port="80"
failureMessage="Login failed: ${1}"
http-version="1.1">
<!--method="POST"-->
<!--successMatch="Aaron"-->
<parameter key="response" value="303"/>
<parameter key="j_username" value="user"/>
<parameter key="j_password" value="pass"/>
<parameter key="j_q" value="/"/>
<parameter key="j_sc" value="http"/>
<parameter key="j_url" value="/app/home"/>
<!-- <parameter key="j_username" value="BLABLAABLAAA.com"/>
-->
<!-- <page host="pmx.sophos.com"
path="/as-sdk/2.x-latest/linux/antispam.tgz.md5"
method="POST"
successMatch="antispam-2010.8.30.194515-i686-linux.tar.gz" >
<parameter key="j_username" value="dev-as-sdk"/>
<parameter key="j_password" value="3M <at> rgar1tas"/>
-->
</page>
</page-sequence>
</parameter>
</service>
<downtime
begin="0" end="300000" interval="30000"/>
<downtime
begin="300000" end="43200000"
interval="300000"/>
<downtime
begin="43200000" end="432000000" interval="600000"/>
<downtime
begin="432000000" delete="true"/>
</package>
The poller.log shows:
2010-08-31 15:38:58,309 DEBUG [PollerScheduler-70
Pool-fiber2] PollableServiceConfig: Finish polling
9:209.17.179.239:Linux-Anitspam using pkg LinuxAntispam result =Down
But what constitutes Down? I am start to do a “Red
Green” on this and duck-taping several different pieces together to try
to get it to give me some good news. Again all that is needed is to login
to the site and record the time it takes to alert if it exceeds a certain
threshold.
TIA
Bill
Paulson
Senior Systems Engineer
email: Bill.Paulson <at> sophos.com
tel: +1 614 923 6280
SOPHOS - simply secure
RSS Feed