I made a proposal for implementing crash report services, so I’ll introduce the content.

Implementation Benefits

Using crash report services automatically transfers error information to the crash report server when errors occur. Then you can view information such as parameters and stack traces when errors occur from a browser, enabling smooth bug handling after releases.

Crash Report Services

I'll introduce four famous crash report services. One is OSS, and the other three are external services.

Our company runs Errbit on Heroku. (Monthly cost $7)

Among the others, Sentry and Bugsnag offer free trial plans as external services, and their paid plans at $29 per month are affordable and easy to implement.

Errbit

• https://errbit.com/
• https://github.com/errbit/errbit

Advantages

• OSS
• Lowest monthly cost

Disadvantages

• errbit requires initial setup
• (However, except for setup, no particular operational costs are required)

Sentry

• https://sentry.io/pricing/

Hobbyist Free

10k events/mo One user 7 day history

Small $29/month

100k events/mo Unlimited users 90 day history

bugsnag

• https://www.bugsnag.com/pricing/

FREE $0 per month Free with 7,500 events per month and 1 seat

TEAM $29 per month Starting at 150,000 events per month and 5 seats

Airbrake

• https://airbrake.io/pricing

I thought it would be difficult to try since there’s no free plan.

ESSENTIAL $49/month

Crash Report Service Implementation Summary

If you want to minimize financial costs, I recommend errbit. If you can pay around 3000 yen per month, I recommend Sentry or Bugsnag.

I couldn’t understand the significant difference in paying 5000 yen per month for Airbrake compared to Sentry and Bugsnag, so choosing Airbrake would be an option if it’s a better service.

That’s all from the Gemba where I want to promote a development system that implements crash report services and fixes bugs immediately.