Page 2 of 2
Re: check_http with regex
Posted: Thu Nov 19, 2015 7:22 pm
by Box293
In $ARG3$ try:
Code: Select all
("\;status"\;:\s"\;SUCCESS"\;,|<string>\[\]</string>)
Re: check_http with regex
Posted: Fri Nov 20, 2015 10:39 am
by haile711
hey Box,
I tried your suggestion too, the yield the same result.
Re: check_http with regex
Posted: Fri Nov 20, 2015 1:52 pm
by lmiltchev
Leave the $ARG3$ wrapped in double quotes in your command:
modify your service by placing the following in the $ARG3$ field in the CCM:
Code: Select all
("status":\s"SUCCESS",|<string>\[\]<string>)
save and apply configuration. Don't test the check in the CCM. Go to Service Detail-><your service>->Force an immediate check. Did this change anything?
Re: check_http with regex
Posted: Fri Nov 20, 2015 4:29 pm
by haile711
I did just as suggested, but got HTTP CRITICAL "pattern not match", but this string is there in the link
This is the output from the page
Code: Select all
<object-stream>
<map>
<entry>
<string>apollo.replication.status</string>
<string>
[ { "slaveReplicationRecords": [ { "status": "SUCCESS", "scope": "", "finished": "11/20/2015 04:42:37",
Re: check_http with regex
Posted: Sun Nov 22, 2015 9:27 pm
by Box293
Is there any change that this is a publicly available URL that we can test against. It can be hard to test some of this regex stuff without being able to test it ourselves.
If that's not possible, I think we should take this into a support ticket so we can help you through a remote session.
Please send an email to
[email protected] referencing this forum thread and we'll take it from there. Reply to this thread when you have done this so we can confirm we received the email.
Re: check_http with regex
Posted: Mon Nov 23, 2015 10:12 am
by haile711
Good morning Box,
Unfortunately, this URL is not accessible publicly. Can I paste the whole strings here? or upload the page in a text file?
I have email to xisupport also. Thanks
Re: check_http with regex
Posted: Mon Nov 23, 2015 11:05 am
by rkennedy
I see your ticket, as this has been received we will now move this into a ticket.