Fly.io Machine and Health Change Feed

Overview

The general app platform does not document a customer-configurable webhook subscription and signing surface, so this route uses supported change detection through Machines reads and state waits, health status, deployment evidence, and documented log shipping. Extension-provider machine-event webhooks are a separate partner-specific contract and are not assumed here.

Prerequisites

• Selected signal types, apps, regions, process groups, and service objectives
• Durable last-seen state, deduplication key, overlap policy, and sink acknowledgement
• Read-only token and redaction rules for Machine, health, release, and log fields

Instructions

Step 1: Choose supported signals

Use Machine list or get for inventory, the Machine wait endpoint for a known transition, health-check status for routing readiness, release evidence for deployments, and documented log shipping for application events.

Step 2: Snapshot the starting boundary