I have installed a new NetXMS system on an Ubuntu server to test the newest release and some new ideas for our existing install.
Previously we had used email for our alerting platform, but it has some issues, and we would like to attempt to use Slack as a possible alterantive, however when I configure the Notification Channel for Slack I am not getting anywhere and the error on the Notification Channel setup is Status: failure, Error Message: Driver Error
It is a brand new base install of NetXMS with the WebGui added... and a few nodes monitored.
I have configured a webhook for slack, and added the following configuration in the Notification Channel setup for Slack:
username=monitor
url=[https://hooks.slack.com/services/***** private info here *****]
I am not sure what I am doing wrong?
Thank you.
Hi,
"Driver Error" is as generic as it looks - it only means the driver loaded, your config parsed, and the POST to the webhook came back with something other than HTTP 200 and a body of exactly "ok". A transport failure, a non-200 code and an error string from Slack all end up as that same message. (If the driver itself were missing or unloadable you'd get "Driver not initialized" instead, so that part is fine.)
To get the actual error, in Tools -> Server Debug Console:
debug ncd.slack 7
debug nc 7
then send again and look in the server log (path is set by LogFile in netxmsd.conf, /var/log/netxmsd by default). It will be one of:
- Call to curl_easy_perform() failed - transport level: DNS, TLS, firewall. Note the Slack driver has no proxy option, so if this server reaches the internet through a proxy, that alone will stop it.
- Error response from webhook: HTTP response code is N
- Error response from webhook: <text> - Slack's own error, e.g. channel_not_found or invalid_payload.
Two things worth checking before you do that:
- url must be a classic incoming webhook - https://hooks.slack.com/services/T.../B.../... - which replies with the literal string "ok". A Workflow Builder trigger URL (https://hooks.slack.com/triggers/...) replies with JSON instead, and the driver will report Driver Error even though Slack accepted the message. This is the easiest one to get wrong right now, since Slack pushes you towards Workflow Builder.
- Recipient is mandatory for this driver and goes out as the Slack channel override. If it names a channel that doesn't exist you get channel_not_found back.
Your post shows url= with nothing after it - assuming that's just removed for the forum, but worth confirming the value actually saved.
Thank you for pointing me in the right direction, I had not created the webhook correctly.