Introducing bugsnag to converge backend

[shaluchandwani]

Description

In order to help with troubleshooting issues on staging and productions, we would like to use Bugsnag to log any issues on the environments. Bugsnag is already configured, we just need to use it. In order to improve performance, use Celery to handle tasks so logging is non-blocking.

Type of change

Please select the relevant option

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Others (cosmetics, styling, improvements)
• This change requires a documentation update

How Has This Been Tested?

• Unit
• Integration
• End-to-end

How to Test

• Check the code climate report to see if any file from the fixtures folder violates the file-line-limit
• create an account on bugsnag and put the secret key in .env, then fire any request which creates the error. You should receive an error notification in the bugsnag dashboard and on GraphQl both.
• Follow the instructions on the readme.md file on running tests. Check to see if tests run successfully

Checklist

• My changes generate no new warnings
• My code follows the style guidelines of this project
• I have linted my code prior to submission
• Existing unit tests pass locally with my changes
• Implementation works according to expectations

JIRA

CV3-92