Redgate Monitor 14

About Slack notifications

You can set up Redgate Monitor to push alert notifications to a Slack channel of your choosing.

Notification behavior is entirely configurable. You can set up Redgate Monitor to send a Slack message when:

alerts are raised.
an alert level increases (e.g. from Medium to High).
an alert ends.

Redgate Monitor's Slack integration is designed to send all notifications to one URL in Slack.

Alternatively, if you prefer to specify routing logic in Redgate Monitor, see Sending email notifications to Microsoft Teams and Slack channels which allows you to configure multiple destinations for alert notifications.

Configuring Slack notifications

Go to the Configuration page. Under Alerts and Metrics, select Notification settings:

Configuring Redgate Monitor to send Slack notifications

Choose when Redgate Monitor should send messages to Slack.
Go to https://api.slack.com/incoming-webhooks and set up an incoming webhook integration.
Enter the Webhook URL into the Slack WebHook URL box.
Click Send Test Notification to check Redgate Monitor can send messages to your Webhook.
You can choose how many notifications each alert type can send for each monitored object in a 24-hour period. The default limit is 30 notifications, and it can’t be set lower than 1.
(Optionally) Provide a channel to post messages into (messages will go to the default channel for the webhook if no channel is specified).
(Optionally) Provide a username that will be used to post messages into Slack (the Slack bot incoming-webhook will be used if no username is specified).

Proxy configuration

If using a proxy, you will need to configure SQL Monitor to use your proxy settings. SQL Monitor 10.2.0 through 10.2.3 does not support setting a proxy.

Go to the machine running the base monitor service.
Open file %PROGRAMDATA%\Red Gate\SQL Monitor\RedGate.SqlMonitor.Engine.Alerting.Base.Service.exe.settings.config and insert either of the following immediately below <networkSettings>, substituting the settings as appropriate.

<!-- Settings with bypass list -->
<defaultProxy address="http://192.168.1.10:8888" useDefaultCredentials="true" bypassLocal="true">
    <bypassList>
      <add address="http://example.com" />
      <add address="http://example2000.com" />
    </bypassList>
</defaultProxy>

<!-- Settings with no bypass list -->
<defaultProxy address="http://localhost:6000" useDefaultCredentials="true" bypassLocal="true" />

If not present, the following should also be added to the <configSections> section

<section name="defaultProxy" type="RedGate.SqlMonitor.Common.Networking.Configuration.DefaultProxySettingsSection, RedGate.SqlMonitor.Common.Networking" />

Save this file and restart the base monitor service

Go to the machine running the base monitor service.
Navigate to %ProgramFiles%\Red Gate\SQL Monitor\

Open RedGate.SQLMonitor.Engine.Alerting.Base.Service.exe.settings.config and insert your proxy settings within a system.net element within the configuration element. An example is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!-- Other config elements... --> 
  <system.net>
    <defaultProxy>
      <proxy usesystemdefault="true" proxyaddress="http://192.168.1.10:8888" bypassonlocal="true" />
      <bypasslist>
        <add address="[a-z]+\.example\.com" />
      </bypasslist>
    </defaultProxy>
  </system.net>
</configuration>

Save this file and restart the base monitor service.

Redgate Monitor 14

Setting up Slack notifications

About Slack notifications

Configuring Slack notifications

Configuring Redgate Monitor to send Slack notifications

Proxy configuration