Proxy config ignored

[Andy Allan]

Looks like the updated plugin doesn't adhere to proxy settings.

I'm assuming similar to what was reporting in issue #2

[Andy Allan]

Just for confirmation, here's the error from Graylog:

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to events.pagerduty.com:443 [events.pagerduty.com/44.231.93.240, events.pagerduty.com/35.167.69.145, events.pagerduty.com/44.233.86.211] failed: Connection timed out (Connection timed out)

But if I use Curl, which does pick up the proxy settings (http_proxy, https_proxy, no_proxy), then it works just fine.

andyallan@graylog1:~$ curl -H "Content-Type: application/json" -X POST https://events.pagerduty.com/v2/enqueue -d '{
  "payload": {
    "summary": "Sending a test from Graylog server using Curl",
    "timestamp": "2020-07-29T16:10:00.000+0000",
    "source": "graylog1",
    "severity": "info",
    "component": "Test",
    "group": "Test",
    "class": "deploy",
    "custom_details": {
      "ping time": "1500ms",
      "load avg": 0.75
    }
  },
  "routing_key": "<redacted>",
  "dedup_key": "123abc",
  "links": [
    {
      "href": "<redacted>",
      "text": "Link to Graylog"
    }
  ],
  "event_action": "trigger",
  "client": "Graylog",
  "client_url": "<redacted>"
}'
{"status":"success","message":"Event processed","dedup_key":"123abc"}
andyallan@graylog1:~$

[Rob Curtis]

We are currently in the process of migrating the Pager Duty plugin into the graylog-plugin-integrations repo. As part of bringing Pager Duty into our "official" repos, we're replacing the Apache HTTP implementation with OkHttp, which is what we use for our HTTP connections elsewhere in Graylog and which honors the proxy settings.