RealDevSquad / RealDevSquad/website-backend
[RFC] adding error logging service to RDS backend
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Why do we need error logging service?
- currrently if we get any 500 error or anything like that, we have to spend a lot of time in figuring out the solution for it, these things can debugged easily if we have a error logging service in our backend which logs these errors and we can easily find the issues and fix them
- Following are the pricing of some of the alternatives that we can use in our backend
Sentry
cost
Rollbar
cost
it only provides us with 5k events per month
BugSnag
- it provides us with 7k events per month in the free tier
- it can provide notification through email
LogRocket
Conclusion
sentry seems to be the best in terms of the free plan they provide, it also provides us with email notifications, which can also be helpful to us
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The RFC names no files, tests, or entry points. Start by reviewing the Sentry, Rollbar, BugSnag, and LogRocket comparison and establish the backend integration scope; done should be a decided service and an agreed implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100