Setup and configuration - Discord
What this integration sends
The Discord integration is a feature of the DockRay panel - the notification channel posts to a chosen Discord channel whenever the scheduler or the ingest pipeline detects one of five monitoring events:
- ping - the application server stops responding,
- ssl - the certificate is about to expire,
- google-page-speed - a performance drop,
- issue - a new error, never seen before,
- error-spike - a sudden surge in the number of errors.
Each event type has its own switch and can go to a different channel on the same Discord server.
Preparing things in Discord
- Create an application in the Discord Developer Portal and add a bot to it.
- Copy the bot token from the Bot tab.
- Invite the bot to your server with an OAuth2 link that includes the
botscope. - Grant it View Channel, Send Messages and Embed Links on the channels where alerts should appear.
- Copy the ID of every target channel (Discord developer mode → right-click the channel → Copy Channel ID).
DockRay identifies a channel only by its numeric ID, never by name - Discord allows two channels with the same name on one server, so a name would not be unambiguous.
Configuring it in the DockRay panel
There is one screen for the account and one for a project: Settings → Notification channels, and for a single project, Project settings → Notification channels. Editing requires the project-management permission, held by the developer role and above.
- Enable the Discord provider and paste the bot token.
- For each event type, enter the channel ID - a string of 17 to 20 digits; any other shape is rejected immediately.
- Save. Leaving the token field blank on save means 'keep what is stored'.
A project inherits the account's configuration by default and can override it with its own bot and channels, or turn a given event type off, independently of the account's settings.
The test message
Every event type has a Send test button. It only works once the token is saved or just entered and the channel field holds a valid ID. A successful test also confirms that the bot actually has permission to post in the target channel, not just that the token is valid.