home.social

#rollbar — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rollbar, aggregated by home.social.

  1. So if you're using #Rollbar and you use `deliver_now` and then try to capture any errors with a `rescue`, you'lll discover that... well... They still get reported to Rollbar!

    Turns out, Rollbar automatically instruments `ActionMailer::MailDeliveryJob` and `deliver_now` uses `ActionMailer::MailDeliveryJob` under the covers, even tho the mail is being delivered synchronously!

    Anyway, that particular "gotcha!" cost us about 80 engineering hours. Should we have given up sooner? Probably...

    #Ruby #Rails #ActionMailer

  2. So if you're using #Rollbar and you use `deliver_now` and then try to capture any errors with a `rescue`, you'lll discover that... well... They still get reported to Rollbar!

    Turns out, Rollbar automatically instruments `ActionMailer::MailDeliveryJob` and `deliver_now` uses `ActionMailer::MailDeliveryJob` under the covers, even tho the mail is being delivered synchronously!

    Anyway, that particular "gotcha!" cost us about 80 engineering hours. Should we have given up sooner? Probably...

    #Ruby #Rails #ActionMailer

  3. So if you're using #Rollbar and you use `deliver_now` and then try to capture any errors with a `rescue`, you'lll discover that... well... They still get reported to Rollbar!

    Turns out, Rollbar automatically instruments `ActionMailer::MailDeliveryJob` and `deliver_now` uses `ActionMailer::MailDeliveryJob` under the covers, even tho the mail is being delivered synchronously!

    Anyway, that particular "gotcha!" cost us about 80 engineering hours. Should we have given up sooner? Probably...

    #Ruby #Rails #ActionMailer

  4. So if you're using #Rollbar and you use `deliver_now` and then try to capture any errors with a `rescue`, you'lll discover that... well... They still get reported to Rollbar!

    Turns out, Rollbar automatically instruments `ActionMailer::MailDeliveryJob` and `deliver_now` uses `ActionMailer::MailDeliveryJob` under the covers, even tho the mail is being delivered synchronously!

    Anyway, that particular "gotcha!" cost us about 80 engineering hours. Should we have given up sooner? Probably...

    #Ruby #Rails #ActionMailer

  5. So if you're using #Rollbar and you use `deliver_now` and then try to capture any errors with a `rescue`, you'lll discover that... well... They still get reported to Rollbar!

    Turns out, Rollbar automatically instruments `ActionMailer::MailDeliveryJob` and `deliver_now` uses `ActionMailer::MailDeliveryJob` under the covers, even tho the mail is being delivered synchronously!

    Anyway, that particular "gotcha!" cost us about 80 engineering hours. Should we have given up sooner? Probably...

    #Ruby #Rails #ActionMailer

  6. One thing I was missing on Cloudflare Pages is better errors' #observability. As I don't use Sentry, there was no easy way to use Rollbar. Until today. I published the #Rollbar plugin for #CloudflarePages to NPM. github.com/hckr-studio/cloudfl

  7. One thing I was missing on Cloudflare Pages is better errors' #observability. As I don't use Sentry, there was no easy way to use Rollbar. Until today. I published the #Rollbar plugin for #CloudflarePages to NPM. github.com/hckr-studio/cloudfl

  8. One thing I was missing on Cloudflare Pages is better errors' #observability. As I don't use Sentry, there was no easy way to use Rollbar. Until today. I published the #Rollbar plugin for #CloudflarePages to NPM. github.com/hckr-studio/cloudfl

  9. #Rollbar provides an efficient way to log errors from
    #CraftCMS without requiring a plugin. This streamlined approach can enhance the efficiency of your error-logging tasks.

    johnhenry.ie/articles/2024/08/

  10. W00t. My little writeup from Rollbar is live! rollbar.com/blog/alisons-story #Rollbar

    I genuinely and truly love Rollbar as a service. Adding it to customer installs is one of the smartest choices I made when I started Grokability, and it's one that pays for itself several times over every single month.

  11. W00t. My little writeup from Rollbar is live! rollbar.com/blog/alisons-story #Rollbar

    I genuinely and truly love Rollbar as a service. Adding it to customer installs is one of the smartest choices I made when I started Grokability, and it's one that pays for itself several times over every single month.

  12. W00t. My little writeup from Rollbar is live! rollbar.com/blog/alisons-story #Rollbar

    I genuinely and truly love Rollbar as a service. Adding it to customer installs is one of the smartest choices I made when I started Grokability, and it's one that pays for itself several times over every single month.

  13. W00t. My little writeup from Rollbar is live! rollbar.com/blog/alisons-story #Rollbar

    I genuinely and truly love Rollbar as a service. Adding it to customer installs is one of the smartest choices I made when I started Grokability, and it's one that pays for itself several times over every single month.

  14. W00t. My little writeup from Rollbar is live! rollbar.com/blog/alisons-story #Rollbar

    I genuinely and truly love Rollbar as a service. Adding it to customer installs is one of the smartest choices I made when I started Grokability, and it's one that pays for itself several times over every single month.

  15. Here's an example of a Hanami provider in my app that configures an exception notifier.

    Notice that:

    1) It only starts in production env
    2) Configuration is separated via `prepare` step
    3) We set Rollbar as a regular error logger. This means that in other envs no special code is needed. You just do `logger.error(e)`
    4) It's 🆒

    I *could* even add `stop` step that disables Rollbar but it's not needed in my app.

    #hanami #ruby #framework #rollbar #webdev #webdevelopment #opensource #oss

  16. Here's an example of a Hanami provider in my app that configures an exception notifier.

    Notice that:

    1) It only starts in production env
    2) Configuration is separated via `prepare` step
    3) We set Rollbar as a regular error logger. This means that in other envs no special code is needed. You just do `logger.error(e)`
    4) It's 🆒

    I *could* even add `stop` step that disables Rollbar but it's not needed in my app.

    #hanami #ruby #framework #rollbar #webdev #webdevelopment #opensource #oss

  17. Here's an example of a Hanami provider in my app that configures an exception notifier.

    Notice that:

    1) It only starts in production env
    2) Configuration is separated via `prepare` step
    3) We set Rollbar as a regular error logger. This means that in other envs no special code is needed. You just do `logger.error(e)`
    4) It's 🆒

    I *could* even add `stop` step that disables Rollbar but it's not needed in my app.

    #hanami #ruby #framework #rollbar #webdev #webdevelopment #opensource #oss

  18. Here's an example of a Hanami provider in my app that configures an exception notifier.

    Notice that:

    1) It only starts in production env
    2) Configuration is separated via `prepare` step
    3) We set Rollbar as a regular error logger. This means that in other envs no special code is needed. You just do `logger.error(e)`
    4) It's 🆒

    I *could* even add `stop` step that disables Rollbar but it's not needed in my app.

    #hanami #ruby #framework #rollbar #webdev #webdevelopment #opensource #oss

  19. Here's an example of a Hanami provider in my app that configures an exception notifier.

    Notice that:

    1) It only starts in production env
    2) Configuration is separated via `prepare` step
    3) We set Rollbar as a regular error logger. This means that in other envs no special code is needed. You just do `logger.error(e)`
    4) It's 🆒

    I *could* even add `stop` step that disables Rollbar but it's not needed in my app.

    #hanami #ruby #framework #rollbar #webdev #webdevelopment #opensource #oss