service-monitoring-setup

Automate Healthchecks.io and UptimeRobot monitoring setup for Cloud Run Jobs and VM endpoints.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/terrylica/gapless-network-data --skill service-monitoring-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-monitoring-setup
Source: https://github.com/terrylica/gapless-network-data/tree/main/.claude/skills/archive/service-monitoring-setup
Command: npx skills add https://github.com/terrylica/gapless-network-data --skill service-monitoring-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Ensures your critical services and jobs are always monitored externally, preventing single points of failure and providing immediate alerts for downtime or missed schedules. It solves the problem of unreliable monitoring and alert fatigue by providing a robust, dual-pipeline monitoring architecture.

Core Features & Use Cases

  • Dual-Service Monitoring: Combines Healthchecks.io (Dead Man's Switch for ephemeral jobs) and UptimeRobot (HTTP polling for persistent services) for comprehensive, external coverage.
  • Pushover Integration: Get critical alerts directly to your mobile device, ensuring you never miss an incident, even when away from your desk.
  • Automated Setup: Programmatically create and manage monitors via API, reducing manual configuration errors and ensuring consistent monitoring policies.
  • Use Case: Set up monitoring for your daily Cloud Run data collection job (Healthchecks.io) and your always-on VM API endpoint (UptimeRobot), with all alerts routed to your Pushover app, all for $0/month.

Quick Start

Set up external monitoring for my Cloud Run job and a VM API endpoint. Configure Pushover alerts for both. The Cloud Run job runs every 2 hours, and the VM API is at 'https://my-vm-ip:8000/health'.

Frequently Asked Questions about service-monitoring-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up external monitoring for Cloud Run jobs and VM endpoints?

External monitoring combines Healthchecks.io for ephemeral Cloud Run jobs (heartbeat-based alerts when jobs miss their schedule) and UptimeRobot for persistent VM endpoints (HTTP polling). This dual-pipeline approach prevents single points of failure and ensures you're alerted immediately to downtime or missed job runs.

Can I use Healthchecks.io and UptimeRobot together for comprehensive service monitoring?

Yes. Healthchecks.io acts as a Dead Man's Switch for scheduled jobs—your job pings it on success, triggering an alert if the ping doesn't arrive by deadline. UptimeRobot continuously polls HTTP endpoints. Together they provide heartbeat and availability monitoring, with alerts routed through Pushover or Telegram.

How do I automate alert routing to Pushover for monitoring events?

Both Healthchecks.io and UptimeRobot integrate with Pushover via API. You configure your monitor with a Pushover integration, then critical alerts bypass email and go directly to your mobile device, ensuring you never miss downtime notifications even when away from your desk.

What's the cost of setting up Healthchecks.io and UptimeRobot monitoring?

Both services offer free tiers that cover production-ready monitoring: Healthchecks.io provides unlimited checks and Pushover integration at no cost, and UptimeRobot includes 50 monitors with 5-minute polling intervals free. Combined monitoring and alerting for Cloud Run and VM services costs $0/month within free-tier constraints.

Do I need to manually create monitors in Healthchecks.io and UptimeRobot, or can I automate setup?

Setup is fully automated via API. The Skill programmatically creates and manages monitors across both services using the requests library, reducing manual configuration errors and ensuring consistent monitoring policies. Doppler integration retrieves secrets, eliminating hardcoded credentials.

Why use external monitoring instead of relying on built-in Cloud Run and VM logs?

External monitoring avoids single points of failure in your infrastructure. If your cloud provider's logging is down or if you lose access to your account, external monitors at Healthchecks.io and UptimeRobot remain independent, still alerting you to downtime. This redundancy is critical for production services.