Route Cron Job Failures to Opsgenie On-Call
CronJobPro sends structured Opsgenie alerts the moment a scheduled job fails, recovers, or gets disabled by the circuit breaker — so the right engineer is paged without delay. Connect your Opsgenie API integration in minutes and let your on-call rotation handle the rest.
Start freeHow Opsgenie alerts work
When a cron job returns a non-2xx response, times out, or hits a connection or DNS error after your configured retries, CronJobPro immediately creates an alert in Opsgenie so your on-call rotation is notified. The same channel fires when a job recovers or when the circuit breaker auto-disables a job after repeated consecutive failures. You can set an alert threshold to suppress noise until N consecutive failures have occurred before any alert is raised.
Set up Opsgenie notifications
You'll need your Opsgenie API Integration Key.
- 1
Create an API integration in Opsgenie
In your Opsgenie account go to Settings → Integrations → Add Integration and choose the API type. Give it a descriptive name (e.g. "CronJobPro") and save. Copy the API Key shown on the integration detail page.
- 2
Note your Opsgenie region
Opsgenie operates on two API endpoints: US (api.opsgenie.com) and EU (api.eu.opsgenie.com). Check which region your Opsgenie account is on — this is shown in your account URL or under Settings → Account.
- 3
Add the channel in CronJobPro
In CronJobPro go to Settings → Notifications and click Add Channel. Select Opsgenie, paste your API Integration Key, and choose your region (US or EU). Save the channel.
- 4
Attach the channel to your jobs or monitors
Open a cron job or heartbeat monitor and select the Opsgenie channel under its notification settings. Any job without a channel attached will not send alerts, so make sure each critical job is covered.
- 5
Optionally configure an alert threshold
If you want to suppress transient failures, set the alert threshold on a job to N consecutive failures before CronJobPro raises an alert. This prevents a single flaky request from paging your team at 2 AM.
- 6
Trigger a test failure and verify
You can temporarily point a test job at a URL that returns a non-2xx status to confirm an Opsgenie alert is created and routed to the correct on-call policy before relying on the integration in production.
Frequently asked questions
What events trigger an Opsgenie alert from CronJobPro?
CronJobPro creates an Opsgenie alert on three events: a job failure (non-2xx response, timeout, or connection/DNS error after your configured retries), a job recovery (the next successful run after a failure), and an auto-disable event when the circuit breaker disables a job after repeated consecutive failures.
Does CronJobPro support both the US and EU Opsgenie APIs?
Yes. When you add the Opsgenie channel in Settings → Notifications you select either the US region (api.opsgenie.com) or the EU region (api.eu.opsgenie.com) to match your Opsgenie account.
Can I monitor heartbeats and dead-man's-switch jobs with Opsgenie alerts?
Yes. CronJobPro monitors both scheduled HTTP cron jobs and heartbeat (dead-man's-switch) monitors. If a heartbeat check-in stops arriving within the expected window, CronJobPro treats it as a failure and will alert the Opsgenie channel attached to that monitor.
How do I avoid alert fatigue for flaky jobs?
Use the alert threshold setting on each job to require N consecutive failures before CronJobPro sends an alert. This means a single transient error is retried and ignored unless the job continues to fail, keeping your Opsgenie alert volume meaningful.
Other integrations
Monitor your cron jobs in Opsgenie
Schedule HTTP jobs and heartbeat monitors, then get failure and recovery alerts where your team already works.