Activity overview
Latest activity by mrhcarlin
Russell D said:
It's not yet possible I'm afraid. We're hoping to support templating in the near future, so this should be possible but currently your suspicion is correct.
Thanks. I'll keep an eye out for it in future releases. / comments
Russell D said:
It's not yet possible I'm afraid. We're hoping to support templating in the near future, so this should be possible but currently your suspicion is correct.
Thanks. I'll keep...
Russell D said:
Does passing a webhook to your Teams install require authentication?
It does not, which I mainly know from having set up two other incoming webhooks to Teams. I'm really leaning towards the issue being that Teams can't translate the JSON payload that SQL Monitor sends. Do you know if it's possible to modify the JSON so I can tailor its layout? There's an example in the link below, but I can't find anything like it in installation directory... One of the other two webhooks that I set up required customization of the JSON, so I'm hoping that this is possible with SQL Monitor. https://documentation.red-gate.com/sm9/configuring-sql-monitor/setting-up-webhook-notifications-preview / comments
Russell D said:
Does passing a webhook to your Teams install require authentication?
It does not, which I mainly know from having set up two other incoming webhooks to Teams.I'm really leanin...
Webhook notifications to Microsoft Teams? (Currently doesn't seem to work)
So on one of my Teams channels I've added an "incoming webhook" connector and put the URL it gave me in SQL Monitor's webhook notifications setting. Now I realise that this feature is in preview, s...
Hi @Russell D ! Yes, I forgot I posted on the forum also hence not updating! In case anyone else comes across this thread with a similar issue, I noticed some stuff related to SSL in the log files retrieved on the SQL Monitor itself (such as "System.Net.WebException: The underlying connection was closed:
Could not establish trust relationship for the SSL/TLS secure channel.") and it turned out that the self-signed certificate I created in IIS did not match the CNAME I was using because the certificate was issued to the FQDN of the server instead. I had to use PowerShell to create a new self-signed certificate issued to the CNAME instead. Instructions can be found easily enough online, but the code I used to create the self-signed certificate is as follows: New-SelfSignedCertificate -CertStoreLocation Cert:\LocalMachine\My -DnsName "<your IIS hostname>". Then I just binded the new certificate in IIS and all was good!
/ comments
Hi @Russell D !Yes, I forgot I posted on the forum also hence not updating!In case anyone else comes across this thread with a similar issue, I noticed some stuff related to SSL in the log files re...