heartbeat_id in the path. This endpoint returns a list of recorded heartbeat events, allowing you to track when check-ins were received and whether they were successful or missed.You can use query parameters like
limit to control the number of results and last_received_at to fetch events after a specific timestamp, which is useful for pagination or incremental analysis.Use cases:
- Incident analysis — Review missed heartbeats and their timestamps to understand when a job failed to report in.
- System auditing — Verify whether jobs or scripts checked in during critical time windows.
- Monitoring history — Build a timeline of all heartbeat events for visualization or reporting.
