[Request] SentryIO connection

[scarecr0w12]

Would be nice to get SentryIO connection, or another issue tracking system.

[vladfrangu]

Technically this is a Issue Tracking system, but marked as a suggestion

[scarecr0w12]

I didn't explain very well. SentryIO allows if a error occurs within the system to be ported into SentryIO. Red-Discordbot has a cog for it. Allows me as a the sysadmin to see when the bot catches an error, or has a problem and lets me react quicker instead of waiting for me to notice the bot is down or someone using the bot telling me.

[vladfrangu]

Interesting. This would be useful after we fix Spam Handling, and any issues like uncaught promise rejections.

Could you provide an example of a way to set it up, if possible in JavaScript? Otherwise python would do

[scarecr0w12]

Of course:

Here is Sentrys main API setup (Can be used with Raven) https://github.com/getsentry/sentry

And Red-Discordbots usage of Sentry (In python tho): https://github.com/Kowlin/refactored-cogs/tree/master/sentry (Secondary ) https://github.com/tekulvw/Squid-Plugins/tree/master/sentryio

[vladfrangu]

Reading through Socket.io, while it would seem very useful, I don't know how we can implement it.

Its required in the webpage, and that might not work as expected. If there's a way we can implement it in WebServer.js file, that would be amazing. Ping @HilbertGilbertson to see if its doable

[scarecr0w12]

So after some digging, combining PM2 with KeyMetrics.io's free system, works the same as Sentrys (If not a little better in how it looks as it tracks more)

[vladfrangu]

And it uses PM2, the thing we should always use when using this bot.

[Gilbert142]

This suggestion is very much not dead yet. It's a possibility for an upcoming 5.X version, because we'd have to rewrite the current way we handle errors (possibly standardizing them into a single system).

[Gilbert142]

With the introduction of the new Logger instance for all our logging and error needs, we've integrated Sentry logging :)