Track completed exports from an Astro server endpoint
A concrete Astro endpoint pattern for recording completed exports in Butters, with server-only credentials, stable user IDs, and a clear failure policy.
6 articles tagged API.
A concrete Astro endpoint pattern for recording completed exports in Butters, with server-only credentials, stable user IDs, and a clear failure policy.
Add one Express 5 error handler that records failed requests in Butters with a request ID, route, and error type, then alerts the team without leaking customer data.
Avoid lost updates when workers increment the same insight card, and learn why atomic arithmetic doesn't solve duplicate delivery or reconciliation.
A notification you ignore is worse than none, because it teaches you to ignore the next one. Here is how the notify flag and ntfy destinations work in Butters, and a simple rule for which events deserve to reach your phone.
The temptation is to track everything. The useful move is to track the handful of things that happen to your revenue: signups, payments, failures, cancellations. Here is how to pick them, name them, and wire them in without making a mess.
Before you need a dedicated error tracker, you need to know something broke. Here is how to send every unhandled error to Butters with one small function, what goes in tags versus metadata, and where this approach stops being enough.