SQL Server Slack Alerts
SQL Server alerts can be sent from miniDBA to any Slack channel you choose. This can be done differently for all alert types and both minor and major priority levels depending on how active you want the channel to be.
Leveraging Slack's communication platform can help you ensure all team members have visibility into your database alerts. Once a SQL alert is in a Slack channel it can be commented on using Slack's messaging facilities.
From user feedback we know that some people like to setup all major priority SQL alerts get emailed out to team members while both major and minor alerts are sent to Slack. This keeps peoples inboxes from filling with every alert and allows browsing of all alerts by anyone on the channel.
Splitting miniDBA SQL alerts into different Slack channels can be useful. For example having both a minor and major channel lets you only subscribe to major alerts but gives you the ability to see all minor alerts if you wish. This keeps your incoming messaging tailored to exactly how you want it.
Below is an example of the Slack channel content when miniDBA sends it messages from it's alerts:
In the screenshot you can see that major alerts are colored red and minor alerts are orange. Alerts summaries are blue - these show how many alerts are currently active.
Also note that next to the miniDBA logo the source of the alert is shown, either Desktop or Server. It may be a rare occurance to see both sources on the same channel as it is likely that miniDBA Server will be mostly used for alerting as it runs 24*7 as a service.
Finally notice in the Slack message at the bottom that not just the alert title but full details are included - in this case a memory snapshot of the SQL Server.
Configure both minor and major alerts to send to slack by using the check box in each alerts configuration:
Leveraging Slack's communication platform can help you ensure all team members have visibility into your database alerts. Once a SQL alert is in a Slack channel it can be commented on using Slack's messaging facilities.
From user feedback we know that some people like to setup all major priority SQL alerts get emailed out to team members while both major and minor alerts are sent to Slack. This keeps peoples inboxes from filling with every alert and allows browsing of all alerts by anyone on the channel.
Splitting miniDBA SQL alerts into different Slack channels can be useful. For example having both a minor and major channel lets you only subscribe to major alerts but gives you the ability to see all minor alerts if you wish. This keeps your incoming messaging tailored to exactly how you want it.
Below is an example of the Slack channel content when miniDBA sends it messages from it's alerts:
In the screenshot you can see that major alerts are colored red and minor alerts are orange. Alerts summaries are blue - these show how many alerts are currently active.
Also note that next to the miniDBA logo the source of the alert is shown, either Desktop or Server. It may be a rare occurance to see both sources on the same channel as it is likely that miniDBA Server will be mostly used for alerting as it runs 24*7 as a service.
Finally notice in the Slack message at the bottom that not just the alert title but full details are included - in this case a memory snapshot of the SQL Server.
Configure the slack channel
Go to the options screen for either miniDBA Desktop or miniDBA Server
- Web hook url - the url of the Slack channel to write messages to
- Channel - the channel name to be sent events
- Username - the Slack username for miniDBA to use
- Send Minor Alerts - enables miniDBA to send both major (sent by default) and minor alerts
- Send Alert Summary - Aggregates all current alerts into a single Slack message
Configure both minor and major alerts to send to slack by using the check box in each alerts configuration: