JetPack Monitor

If you still use Jetpack, you can deactivate the Monitor module by going to Jetpack > Settings in your dashboard.

If you’ve removed Jetpack, I’d suggest disconnecting your site from your WordPress.com to stop Monitor from checking your site. You can follow the instructions here to do so:
https://en.support.wordpress.com/disconnect-jetpack-sites/

I hope this helps.

Hi Jeremy,

I already done that. I did each of this actions but I still receiving logs from the Jetpack Site Uptime Monitor. Right now I don’t have the plugin installed, and the site aren’t linked to my wordpress account, but they still be monitored by the plugin. Can you remove manually my site from the monitoring task?
The url are:
https://www.comeebebe.com
https://www.waltertavares.pt

Greats,
/wt

That seems like a bug. I’ll take a closer look, and get back to you as soon as it’s fixed.

Thanks for reporting the issue!

My site was down for 3 days and jetmon did not notify me.

Looking at the logs I see that jetmon hit my site 530 times on the 15th of August. Over 500 were status code of 500.

I have since fixed the problem plugin but now I am wondering of jetmon is of any use. Site is jdmiles.com

@sniu7y That seems like an issue indeed!

Jetpack Monitor pings your site every 5 minutes, so that would account for 288 pings per day. If it detects that your site is down, it goes into “alert mode”. When that happens, Monitor starts pinging your site every 2 minutes instead of 5. If your site returns an error 3 times in a row, it goes one level deeper and pings your site from different locations around the world, to make sure it’s not just inaccessible from a specific location. Then, and only then, an email is sent (except if an email was already sent earlier to tell you your site was down).

Since your site was hit a lot (530 times a day, so almost twice the normal amount), it’s safe to assume that Jetpack Monitor considered it as down quite a few times. However, if you didn’t receive an email, it could mean that your site then became reachable when Jetpack went into “alert mode”.
We should be able to check that theory by looking at your access logs in details. Would you mind sending us more details via this contact form, and mention this thread?

Thanks!

Initially I only looked at 192.0.84.33. I had not identified the other addresses as jetmon. So there were 1221 pokes on Aug 15th.

Data for Aug 15.
ec2-54-232-116-4.sa-east-1.compute.amazonaws.com 011 of 235
ec2-54-217-201-243.eu-west-1.compute.amazonaws.com 208 of 222
ec2-122-248-245-244.ap-southeast-1.compute.amazonaws.com 001 of 234
192.0.84.33 505 of 530

It is obvious that your algorithm is not going to catch this problem since the one site always (except for one time) returned 200.
Simply put the site was too CPU bound to load the page but seems it could return a 200 enough for you not to flag it.

It is obvious that your algorithm is not going to catch this problem since the one site always (except for one time) returned 200.
Simply put the site was too CPU bound to load the page but seems it could return a 200 enough for you not to flag it.

It seems like it, yes. We could be more strict and alert site owners earlier, but that would generate a lot of false positives. I’m not sure what the right balance should be.

If you have any suggestions, do not hesitate to let me know!

No matter what Jeremy, is it possible to manually stop the monitoring for my sites?
I still have accesses and it’s killing me.

Greats

@walter Yes, we’re still working on it. I’ll post again here as soon as we fix this!

Hi,

Have you anything new to me? I still have downtime cause the dynos can’t rest.

Greats

I believe I may have fixed the issue. Could you let me know if you still see requests from Jetpack Monitor in your logs, starting now?

Thanks!

Hi,

Thanks for your help and feedback, it’s seems ok now. I had a log every 5 minutes and none since 08:56 (server time):

[21/Aug/2015:08:31:51 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:36:39 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:41:45 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:46:47 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:51:39 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)
[21/Aug/2015:08:56:40 +0000] "HEAD / HTTP/1.1" 200 - "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)

Can I use the Jetpack plugin without the monitor feature now? Can I now activate/deactivate the monitor feature?

Greats,
thanks a lot

Can I use the Jetpack plugin without the monitor feature now? Can I now activate/deactivate the monitor feature?

Yes. The problem was caused by a sycnhronization issue between your sites and WordPress.com, but this is now solved, so you will be able to activate and deactivate Monitor as you wish.

Great, thanks a lot.