Hi. It's taken me a while to work out what format the server was expecting it's payload (I had to translate the hook into powershell). I thought it would be good to make a comment on what is epxected by the subversion commit hook.

POST https: //hitched.slack.com/services/hooks/subversion?token=xxxxxx
Content-Type: application/x-www-form-urlencoded
Host: foo.slack.com
Content-Length: 101

payload=%7B%22revision%22%3A1%2C%22url%22%3A%22http%3A%2F%2Fsvnserver%22%2C%22author%22%3A%22digiguru%22%2C%22log%22%3A%22Log%20info%22%7D

That is specifically lowercase JSON parameters with double quotes, and no quotes around the revsision number

{"revision":1,"url":"http://svnserver","author":"digiguru","log":"Log info"}

Any other format returns a "No payload received from svn" response

I got an error (no_text) if I don't add a "text" item to the payload.

This bot doesn't seem to properly encode utf-8 content.
I posted 😁 in a svn commit message (which is correctly parsed by other SVN clients), but the hook sent this to slack: ?\240?\159?\152?\129.

Our jenkins setup correctly parsed the svn commit, and also sent a slack message, with proper formatting. So both SVN and slack correctly handle this, but not the svn hook from this repository.

Is is possible to enable more fields like to the alerts going into slack, for example on an acknowlegement you just get ACKNOWLEDGED, If I add fields for $SERVICEACKAUTHOR$ and $SERVICEACKCOMMENT$ they do not show up in the alert. My service alert script looks like so:

$USER1$/slack-nagios.pl -field slack_channel=#alert -field HOSTALIAS="$HOSTNAME$" -field SERVICEDESC="$SERVICEDESC$" -field SERVICESTATE="$SERVICESTATE$" -field SERVICEOUTPUT="$SERVICEOUTPUT$" -field NOTIFICATIONTYPE="$NOTIFICATIONTYPE$" -field SERVICENOTES="$SERVICENOTES$" -field SERVICEACKAUTHOR="$SERVICEACKAUTHOR$" -field SERVICEACKCOMMENT="$SERVICEACKCOMMENT$"

does this script support downtime notifications? i can see that for service conf you are using w,u,c,r but s is missing.

i have configured nagios to send the downtime notification by using the s flag but nothing gets displayed in slack. in nagios notification history i can see that there was an attempt to send it via your command.

This is a test issue.

My Nagios notification wasn't working; turns out running it manually mentioned /etc/pki/tls/certs/ca-bundle.crt not existing. yum install ca-certificates fixed this.