Error Tracking with Errbit
Common Features Series
1. Liking Posts 2. Markdown and Emoji with the html-pipeline gem 3. Comments With Polymorphic Associations 4. Activity Feed From Scratch 5. @Mentions, Autocomplete, Notifications, and Links 6. Scheduling Posts 7. In-App Navbar Notifications 8. Repost / Retweet / Reblog 9. Message Templates 10. Improving In-App Notifications 11. Devise Masquerade as another User 12. Select Or Create Field With Selectize.js 13. Preferences & Settings with ActiveRecord::Store 14. Global Autocomplete Search 15. Charts with Chartkick and Groupdate 16. Analytics with Segment 17. Tracking Metrics with Ahoy and Blazer 18. Sortable Drag and Drop 19. Using the Trix Editor plus File Upload Attachments 20. Administrate Custom Fields and the Trix Editor 21. Handling Inbound Email Parsing with Rails 22. Two Factor Authentication With Devise 23. Error Tracking with Errbit 24. A/B Split Testing with the Split gem 25. Handle 404s Better Using Rescue_from 26. Undo Sending Button like GMail 27. Auto-detect User Time Zones in Rails 28. User Referral Program From Scratch 29. Fast Pagination with PagyEpisode 215 · November 14, 2017
Track errors in Rails, Sidekiq, etc in production for free using the open source Errbit app and the Airbrake gem
Production Debugging Deployment Errors
Resources
Transcripts
No transcripts available. Earn a free month
Discussion
I am trying to wrap around my head around the hooks. The first immediate hook is errbit knowing the application's github repository. The second is the airbreak.rb file where the app (and I assume all of its deploys) actually points to errbit application and its services. So I understand airbreak config... 'send my errors to errbit'. But why then does errbit need to know about to the repo?
A corollary question: if there are multiple deploys, say 'staging1' and 'staging2' are added, they will all be handled by errbit and show the non-traditional deploy name (unless stated in ignore_environments config line) ?
It asks for your repo so it can link you to the line of code that triggered the error.
And yes, any errors from environments mentioned in ignore, will be skipped.
Login or create an account to join the conversation.