The Invisible Infrastructure
Monitoring for Internal Tools & Background Jobs
Your nightly batch job failed 2 weeks ago. Your data pipeline hasn't run since Tuesday. Nobody noticed because internal tools don't have users who complain.
The Forgotten Infrastructure
Internal tools, admin services, and background jobs are the most neglected parts of any stack. No public URL to ping. No users to complain. When they fail, you find out way too late.
Heartbeat Monitoring
Jobs ping us when they run. No ping = alert.
Internal Agent
Monitor services behind your firewall.
Duration Tracking
Know when jobs run too long or hang.
Exit Code Reporting
Track success and failure of scripts.
Silent Failures
Real failures that went unnoticed for days:
- ✗Backup job stopped after a server update cleared the crontab
- ✗Data sync ran for 48 hours waiting on a database lock
- ✗Queue worker crashed and nobody processed jobs for 3 days
- ✗Admin tool broke because deployment only tested the public app
How We Monitor Internal Systems
Two approaches for services without public URLs:
Heartbeat Endpoints
Jobs ping us. One HTTP call.
Internal Agent
Deploy agent to check services locally.
Schedule Awareness
Set expected run times and grace periods.
Private Status
Internal status page for your ops team.
Getting Started
Set up internal monitoring in a few minutes:
- 1
Create Heartbeat Monitor
Set the schedule (cron expression) and grace period. Get a unique ping URL.
- 2
Add Ping to Your Job
Add
curl https://ping.upti.my/your-idto the end of your script. - 3
Set Up Alerts
Configure where you want to be notified when jobs miss their schedule.
- +
Deploy Agent (optional)
For internal services, deploy the agent to check database and service health.
Frequently Asked Questions
How do I monitor services without a public URL?
Deploy our lightweight agent inside your network, or have your services ping our heartbeat endpoints. Both work behind firewalls.
What about cron jobs and scheduled tasks?
Your cron job pings us when it runs. No ping on schedule? You get an alert. Dead simple.
Can I monitor database connections?
The agent can check database connectivity and run health queries. PostgreSQL, MySQL, MongoDB, Redis, all covered.
How do I monitor background workers?
Workers send heartbeat pings at regular intervals. If the pings stop, the worker stopped. You can also track queue depth.
Is the agent secure?
Outbound connections only. No ports opened, no inbound traffic accepted. All communication encrypted.
Related Topics
Ready to start monitoring?
Set up your first health check in under 2 minutes. No credit card required.