Spoke too soon. org.graylog2.plugin.alarms.callbacks.AlarmCallbackConfigurationException: Configuration error. Couldn't parse socks_proxy correctly. 2016-11-17_15:46:46.67755 at org.graylog2.plugins.slack.callback.SlackAlarmCallback.initialize(SlackAlarmCallback.java:30) ~[?:?] 2016-11-17_15:46:46.67825 at org.graylog2.alarmcallbacks.AlarmCallbackFactory.create(AlarmCallbackFactory.java:43) ~[graylog.jar:?] 2016-11-17_15:46:46.67979 at org.graylog2.periodical.AlertScannerThread.doRun(AlertScannerThread.java:112) [graylog.jar:?] 2016-11-17_15:46:46.68032 at org.graylog2.plugin.periodical.Periodical.run(Periodical.java:77) [graylog.jar:?] 2016-11-17_15:46:46.68116 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_101] 2016-11-17_15:46:46.68168 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_101] 2016-11-17_15:46:46.68236 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_101] 2016-11-17_15:46:46.68275 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_101] 2016-11-17_15:46:46.68342 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_101] 2016-11-17_15:46:46.68396 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_101] 2016-11-17_15:46:46.68465 at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101]
I'll just jump onto the Github page and join in. Thanks! On Wednesday, November 16, 2016 at 11:00:25 AM UTC-5, Jochen Schalanda wrote: > > Hi Tom, > > there's a feature request for this at > https://github.com/Graylog2/graylog-plugin-slack/pull/27, but the current > version of the Graylog Slack plugin doesn't support using HTTP proxies yet. > > Cheers, > Jochen > > Am 16.11.2016 um 16:37 schrieb Tom Vile <tom....@gmail.com <javascript:>>: > > I am using the Slack plugin for callbacks but unfortunately I get "Could > not send message to Slack." In the triggered alerts. I tracked down the > error in the logs and it shows "java.net.ConnectException: Connection > refused" > I assume that it is caused by the fact that we are using a proxy for > outgoing connections and the plugin is not utilizing the proxy config to > route out to the internet. > > Is there a setting somewhere within Graylog to set a proxy variable so > that it uses the proxy for outbound internet connections? > > I am using the latest release of GrayLog. > > Thanks, > > Tom > > > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/72004dc5-98f8-41f2-8ed7-79a412ae14ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
