Automated Sentry Error Tracking

Summary

Fly.io announces Sentry as the default error-monitoring tool for its applications, with new deployments receiving an automatically provisioned Sentry project and existing apps using flyctl ext sentry create. Each organization receives one year of monthly Team Plan credits covering 50,000 error events, 100,000 performance units, 500 session replays, and 1GB of attachment storage. For Rails apps, flyctl launch installs the required gems, creates initializers, and sets the SENTRY_DSN secret, allowing boot failures, memory exhaustion, exceptions, latency issues, and crashes to reach Sentry. The post demonstrates a deliberately raised Ruby exception, then uses flyctl apps errors to open the Sentry issue dashboard and identify the bug; planned extensions include release tracking and out-of-memory events.

Takeaways

1. 1

   Each Fly.io organization receives monthly credits for 50,000 error events, 100,000 performance units, 500 session replays, and 1GB of attachment storage for one year.

2. 2

   Rails auto-instrumentation through flyctl launch installs gems, plants initializers, and configures SENTRY_DSN, including for deployment-time failures such as boot errors and out-of-memory conditions.

3. 3

   The example raises a Ruby exception, receives a Sentry notification, and reaches the issue through flyctl apps errors; future plans include release tracking and out-of-memory events.