Goal: report errors in Github instead of Discord bot

[zolotokrylin]

It is much better to report and discuss problems and solve these problems in Github instead of Discord.

[zolotokrylin]

@georgeciubotaru how do you trouble shoot now with Discord Bot? via custom logger?

[georgeciubotaru]

@zolotokrylin I have the link to the failed task in the Discord message. If you mean how the message comes in Discord, then there is integration with the Discord bot to send messages.

[zolotokrylin]

@georgeciubotaru Discord integration is part of the native function of the Trigger.dev?

[georgeciubotaru]

@zolotokrylin Yes, Trigger.dev has default integrations with Discord Bot and Github.

In our case, we are using custom Github integration as we need more events to handle, but for Discord is straightforward

[zolotokrylin]

@georgeciubotaru does it mean we can create GitHub issue when something wrong happens?

[georgeciubotaru]

@zolotokrylin Yes, we can do that. Don't know if it's a good idea or not (I just wanted to avoid the flooding issue). I can create an issue in case there is an error reported in Discord.

e.g.

Assigning 4 persons to review and something went wrong we are receiving from 4 to 8 messages for each person, that will be 8 issues. Instead, I will define 1 manually that will fix these errors.

[zolotokrylin]

Ok, I just feel that for me it's flooding my discord. And discord is for real time messages, while GitHub is for dev issues handling.

Up to you. I just thought it's logical to triage issues in GitHub and not discord.

[zolotokrylin]

Not urgent. No need to act here. Let's stash it.

[zolotokrylin]

https://discord.com/channels/969416857562017812/1258286610324389888/1258287094380630057