Menu
Feature · Monitoring
Request-managed heartbeat checks for scheduled jobs
Plan heartbeat URLs for backups, sync jobs, imports, reports, and scheduled tasks as an operator-managed setup. Automatic missed-run alerts are planned, not yet live.
- HTTP · DNS · TCP
- live checks
- 1 min
- Team cadence
- Real
- uptime history
- Public
- status page
Ask our team to set up a heartbeat URL for an important scheduled job.
Agree the expected interval and grace period up front.
Self-serve heartbeat creation and automatic missed-run alerts are coming soon.
Monitor
What it checks (operator-managed)
Today, heartbeat coverage is configured with our team. You tell us the job, expected interval, and grace period, and we set up a heartbeat URL for the task to ping on each run.
Response time · 24h
182 msAlerting
Missed-run alerting (planned)
Self-serve heartbeat creation and automatic incidents when a job misses its window are on the roadmap. Until they ship, missed-run detection is reviewed operationally rather than alerted automatically.
Status pages
What customers see
Backup names, file paths, and job internals stay private. Only customer-facing impact appears on public status pages when a scheduled task affects a service.
Looks right either way
Light or dark, your status page stays on-brand.
Match what your customers expect with a clean light or dark public page — same components, same clarity.
Last 90 days · 99.98% uptime
Safe for public status pages
- Website and application availability
- API health endpoint status
- DNS and SSL issues affecting customer access
- Maintenance windows and incident timelines
- High-level region coverage
Internal operations only
- SSH, admin panels, databases, queues, and backups
- Server names, origin IPs, provider IDs, and ports
- Firewall rules, file paths, and secret-related config
- Primary or backup probe node details
- Customer-specific private control panels
Setup workflow
From first check to customer-ready status.
List the scheduled jobs that affect customers, billing, backups, or reporting.
We set up a heartbeat URL with the expected interval and grace period.
When automatic missed-run alerts ship, enable standing alerting for each job.
Decide with confidence
Where request-managed heartbeat checks for scheduled jobs earns its place
A useful monitor is tied to a customer journey, an owner, and a response rule. The goal is not more checks; it is earlier detection with less noise.
Use this when
- Ask our team to set up a heartbeat URL for an important scheduled job.
- Agree the expected interval and grace period up front.
- Self-serve heartbeat creation and automatic missed-run alerts are coming soon.
Set the boundary
- This page includes an operator-assisted step and a capability that is clearly marked as planned. Confirm the current service scope with Faciotech before relying on either workflow for a critical service.
- Keep server names, credentials, provider identifiers, and internal diagnosis out of public status updates.
- Pair uptime evidence with application logs or tracing when the question is why a service failed, not whether customers can reach it.
Product evidence
A real reliability workflow, not a promise deck.
FTStatus earns trust with a product you can inspect and a setup you can test before it becomes part of a customer-critical service.
View live demoA live public experience
Open a real FTStatus status page and inspect the same component, incident, maintenance, and subscription flow your customers will use.
A testable operating loop
Create a monitor, run the check, verify the alert path, publish customer-safe impact, and retain the incident timeline.
Honest capability boundaries
Live, operator-assisted, managed-only, and planned workflows are labelled so buyers can scope the service without hidden assumptions.
Before you choose
Questions buyers ask before setup.
Clear scope now prevents surprise costs, noisy alerts, and public status pages that expose the wrong detail later.
What does request-managed heartbeat checks for scheduled jobs cover?+
Plan heartbeat URLs for backups, sync jobs, imports, reports, and scheduled tasks as an operator-managed setup. Automatic missed-run alerts are planned, not yet live.
What should I configure first?+
Ask our team to set up a heartbeat URL for an important scheduled job. Then test the failure and recovery path before attaching the monitor to customer notifications.
Will technical details appear on the public status page?+
No. Public components describe the affected customer-facing service. Infrastructure details and investigation notes remain in the internal workflow.
Can Faciotech configure and maintain this for us?+
Yes. Managed monitoring can include scope design, monitor setup, alert tuning, status-page maintenance, and incident coordination when included in the agreed service.
Plan monitoring around the service you actually operate.
Map the critical services, owners, alert routes, customer communication, reporting, and response boundaries with Faciotech before rollout.