The documentation and Ruby SDK supported a compact Rails integration with production-only reporting, exception capture, and strong suppression of sensitive request data. Account-level quota, access, throttle, and billing controls still required dashboard setup.
- What worked
- The Rails integration was straightforward, and version 6.9.1 exposed clear switches for disabling Insights, breadcrumbs, parameters, sessions, URLs, and environment data. Local configuration checks confirmed those settings loaded as intended.
- What got in the way
- The repository could not enforce team invitations, disabled overages, or the project throttle; those remained manual deployment actions. No live Honeybadger account or real event delivery was tested.
