This post will provide a more detailed explanation about setting up the schedule of your PushMon URL and when a ping is valid or not to keep the PushMon URL be in UP state.

We will not go over all possible schedules but this will at least give you an idea when to do a ping.

–Comprehensive schedule–

Schedule: “every day” – a ping must be done at least ONCE every 24 hours

Example:

  • Anytime before 12 AM of the next day is a valid ping

Schedule: “every 6 hours” – checking will occur every 12 AM, 6 AM, 12 PM and 6 PM so a ping must be done before these checks.

Example:

  • A ping at 11:30 PM is a valid ping for the 12 AM check.
  • A ping at 12:02 AM is not valid for the 12 AM check, but it will be counted towards the 6 AM check.

Schedule: “every Fri-Sun” – the PushMon URL will only be checked every Friday, Saturday and Sunday .

Example:

  • A single ping on Friday is valid.
  • A ping on Tuesday is valid for the Friday check.
  • A ping on Sunday is valid for the Friday check as well.

–Specific time–

Schedule: “by 12:10 AM every day” – similar to “every day”, a ping must be done at least once every 24 hours. But this time, the checking will start at 12:10 AM

Example:

  • A ping at 11:30 PM is valid.
  • A ping at 12:15 AM is valid for the 12:10 AM check.

Note: “by 12:10 AM every minute” and “by 12:10 AM every hour” is not a valid schedule.
It will also accept minutes divisible of 10 or 5 — “by 12:22 AM” is not allowed.

Schedule: “by 2:00 PM every endOfMonth” – a ping must be done before 2:00 PM at the last day of the current month.

Example:
A ping anytime on the 16th is valid.
A ping at 2:05 PM at the end of month is not valid and it will count towards the next check.

–Advanced schedule–

Schedule: “every Tue within 1 hour” – the PushMon URL must be pinged 1 hour before 12 AM Tuesday check. Pings done earlier won’t count.

Example:

  • A ping at 11:10 PM of Monday is valid.
  • A ping at 11:58 PM of Monday is valid.
  • A ping at 10:30 PM of Monday is not valid and it won’t count for anything.
  • A ping at 12:05 PM of Tueday is also not valid.

Schedule: “every 3 hours within 2 hours” – the ping must be done 2 hours before the next 3rd hour check.

Example:

  • A ping at 1:30 AM is valid for the 3 AM check.
  • A ping at 5:00 PM is valid for the 6 PM check.
  • A ping at 12:20 AM is not valid before it’s more than 2 hours before the 3 AM check.

Note: schedules “within n minutes” is allowed.

We hope that this post will help you use the PushMon service more efficiently.
You may always contact us should you require further assistance.

Thank you for using PushMon!

PushMon service were down for 20 minutes

Please disregard any missed pings from 2:30 PM to 2:50 PM (EST). Our hosting provider had experience an issue.

We apologize for the inconvenience. Thank you for using PushMon.

PushMon was DOWN

Please ignore any missed pings yesterday (October 20) from 3:22 PM to 3:34 AM (EST) as the server were having issues.

We apologize for the inconvenience.

Should there be any more issues or concerns, you may always contact us.

Thank you for using PushMon!

PushMon power issues

Our hosting provider experienced a complete loss of utility power from yesterday from 4:54 PM to 11:24 PM (EST) which lead our servers to go down.  Please ignore alerts of missing pings during this downtime period.

We apologize for the inconvenience.

Should there be any more issues or concerns, you may always contact us.

PushMon was DOWN

Please ignore any missed pings (and possibly consecutive email alerts) from July 13 to 7 AM of July 14 (EST). We were having some temporary server issues.

We apologize for the inconvenience.

Should there be any more issues or concerns, you may always contact us.

Thank you for using PushMon!

PushMON was DOWN

Our data center had issues from 1:16 AM to 1:43 AM (EST). Please ignore any missed pings during this time period. Our apologies for the inconvenience.

Release 1.15

New features for this release:

* Ping Within
When you need your PushMon URL to be pinged on a specific time range, you may add “within” on your schedule. Accepts “hour/s” and “minute/s”.

Schedule example: “every 3:00 PM within 1 hour” – This means that a ping within 2:00 PM to 2:59 PM is valid and will keep your PushMon URL status UP.

Any pings outside the within range is invalid and will make the PushMon URL status DOWN upon its check.

* PagerDuty support
If you have a PagerDuty account and you want to be alerted on PagerDuty, just input your API Key to your PushMon URL.
For more details, here’s how to include your PagerDuty to your PushMon URL.

* Optional Description text box
A text box is added for the PushMon URL’s description. This description is included in the alert to make it easier for the PushMon URL to be distinguished.

* Additional URL alert for UP status.
We have separated URL calls as alerts for DOWN and UP status.
In the URL tab, there’s now a URL text box which will be called for DOWN state and a separate URL text box for UP state.

How to include PagerDuty on your PushMon URL

This guide will help you integrate your PagerDuty account to your PushMon account.

1. Configuring a New Service

On your PagerDuty page, click on Configuration > Services.

1

Click on Add New Service.

2

Fill up information in the fields. Just make sure that Integration Type is set to “Generic API”

3

NOTE: One service is enough for all of your PushMon URLs. If you already have a Generic API service, you may also use that.

2. Getting the API Key of Your Service and Putting it on your PushMon URL

To get the Service Key, click on your newly configured service and look for Integration Key

4

On your PushMon Edit Page, place the Integration Key on the text field under PagerDuty tab.

5

And that’s it. You’re good to go.

PushMon was DOWN

Our data center had issues from 6:08 PM to 6:33 PM (EST). Please ignore any missed pings during this time period. Our apologies for the inconvenience.

PushMon Power Issues

Our data center was down due to power issues from 8:08 AM to 09:07 AM (EST). Please ignore any missed pings during this time period. We apologize for the inconvenience.

Make sure your websites, applications, scripts and background jobs are running.