Go to the "OAauth & Permissions" page for your newly-created app, and add the following scopes under "Bot Token Scopes":
channels:join - Join public channels in a workspace
channels:read - View basic information about public channels in a workspace
chat:write - Send messages as <app>
files:write - Upload, edit, and delete files as <app>
users:read - View people in a workspace
users:read.email - View email addresses of people in a workspace
groups:read - View basic information about private channels that your slack app has been added to
2. Install app at your Workspace
At the "OAuth & Permissions" page, press on "Install to Workspace" in order to generate Slack token:
Create a webhook
Go to the 'Incoming Webhooks' page for your newly-created app and toggle 'Activate Incoming Webhooks' to turn it on. Then click on 'Add New Webhook to Workspace':
Select the channel that the notifications will be posted to:
Lastly, pass the token / webhook to the CLI as a param or in the config.yml file:
Token:
Use the Slack token when you execute edr monitor using the option -st, --slack-token and -ch, --slack-channel-name:
Or just edr monitor if you used config.yml. Please note that when you specify the —slack-channel-name, it’s the
default channel name to which all the alerts will be sent that are not attributed to any custom channel. Therefore,
if you execute several edr monitor commands at the same time with different slack-channel-name arguments, they can
be sent to the wrong one due to the overlap accessing the backend table of elementary. For avoiding this problem,
the guide can be followed.
In order to monitor continuously, use your orchestrator to execute it regularly (we recommend running it right after
your dbt job ends to monitor the latest data updates).
Read more about how to deploy Elementary in production.
If you need help or wish to consult on this, reach out to us
on Slack.