graylog-labs/graylog-plugin-pagerduty

A Graylog plugin that triggers PagerDuty events

graylog-plugin-pagerduty's Issues

Not working

Hi there, I have successfully installed this plugin and added my PagerDuty service key to the configuration. I then set up a test stream with a max. of 1 message in 10 minutes - in the Graylog2 web interface the stream shows that it is in ALERT state, but I have not received any PagerDuty incident notifications. What could I be missing?

Should PagerDuty 2.0 plugin work on Graylog 3.2.5 cluster?

I just deployed a Graylog 3.2.5 cluster on Amazon Linux 2 in AWS.
I installed the new PagerDuty 2.0 plugin in the plugins directory on both hosts before starting the graylog-server service.

I see this in the logs on both hosts:
2020-05-28T10:16:30.412Z INFO [CmdLineTool] Loaded plugin: PagerDutyNotificationPlugin 2.0.0 [org.graylog.plugins.pagerduty.PagerDutyNotificationPluginPlugin]

When I go to the Notifications screen and click Create Notification, I don't see the PagerDuty Notification under Notification Types. I see this:

Could I have missed a step?

Support for Graylog 4

When installing on a Graylog 4.0.1 server it seems to properly load the plugin:

2021-01-07 15:31:24,683 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: PagerDutyNotificationPlugin 2.0.0 [org.graylog.plugins.pagerduty.PagerDutyNotificationPluginPlugin]

However there is no Pager Duty notification option:

I assume there is no Graylog 4 support yet, since I do not see any error in the Graylog logs.

wrong time frame for link

with a condition of x number of message in the last 5 mins to trigger a pagerduty alert, the link in pagerduty is created with a relative timeframe resulting in the wrong logs shown. In other words, it shows the logs from the last 5 mins when I click on the link instead of when the incident was raised

i think the correct behaviour should be an absolute timeframe which trigger the condition so that even when the incident is view one hour later, the timeframe for the logs will still be correct

Proxy config ignored

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

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

Receiving message details

When events are posted to pager duty they don't contain any message information. How do we enable this?

Only supports v3.3

I noticed that the docs claim the updated plugin supports v3.1 and later.

From testing both 3.1 and 3.2, the "PagerDuty Notification" type never appears when creating a new notification.

It's only available on v3.3+

At the very least the docs need updated, but if the intention was indeed for 3.1 and upwards to be supported, a wee bit extra digging will be required.

Publishing your artifacts to the mvnrepository

Is it possible to publish the release JAR file to mvnrepository?

See message details in incident?

Hi, I'd really like to see the message details in the incident message on PD, since sometimes it is critical, but most of the times the message can wait a while.

Is this possible?

graylog2.conf setting http_proxy_uri ignored

It seems like the pagerduty alert plugin is not respecting the http_proxy_uri setting from graylog2.conf.

When I try to send a DummyAlert using the web interface or the REST browser, the request hangs with no response. This is the same behaviour when I try to download a file from the public internet. (These servers require a proxy to make any http connections beyond our walls.)

I can replicate this behaviour on the command line using curl to send an alert to pagerduty. Before executing export http_proxy=http://my.proxy.com:8080/, the request will hang forever. After setting the proxy, the request successfully creates an alert in pagerduty.

Due to the nature of information logged to our servers it is important that we control how these machines access the internet. If application level proxying is available, it is much preferred to setting the proxy server globally.

I'm not a Java developer, but it looks like the http_proxy_uri setting is accessible through the graylog2.BaseConfiguration class, and a quick check for existence would allow it to be used when the URL is made here.

A presumably relevant SO post can be found here: How do I make HttpUrlConnection use a Proxy?

Graylog 3.1 support

It would be good if this plugin would support Graylog 3's new Event Notification system.

Error packaging

Hi all, when running mvn package I am getting

[INFO] --- frontend-maven-plugin:1.6:yarn (yarn run build) @ graylog-plugin-pagerduty ---
[INFO] Running 'yarn run build' in /Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty
[INFO] yarn run v1.12.3
[INFO] $ webpack
[ERROR] /Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/cli.js:93
[ERROR] 				throw err;
[ERROR] 				^
[ERROR]
[ERROR] Error: Cannot find module '/Users/benjamincuthbert/dev/code/rnd/graylog2-server/graylog2-web-interface/manifests/vendor-manifest.json'
[ERROR]     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
[ERROR]     at Function.Module._load (internal/modules/cjs/loader.js:506:25)
[ERROR]     at Module.require (internal/modules/cjs/loader.js:636:17)
[ERROR]     at require (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
[ERROR]     at new PluginWebpackConfig (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/graylog-web-plugin/lib/PluginWebpackConfig.js:25:25)
[ERROR]     at Object.<anonymous> (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/webpack.config.js:6:18)
[ERROR]     at Module._compile (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/v8-compile-cache/v8-compile-cache.js:194:30)
[ERROR]     at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
[ERROR]     at Module.load (internal/modules/cjs/loader.js:598:32)
[ERROR]     at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
[ERROR]     at Function.Module._load (internal/modules/cjs/loader.js:529:3)
[ERROR]     at Module.require (internal/modules/cjs/loader.js:636:17)
[ERROR]     at require (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
[ERROR]     at WEBPACK_OPTIONS (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/utils/convert-argv.js:114:13)
[ERROR]     at requireConfig (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/utils/convert-argv.js:116:6)
[ERROR]     at /Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/utils/convert-argv.js:123:17
[ERROR]     at Array.forEach (<anonymous>)
[ERROR]     at module.exports (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/utils/convert-argv.js:121:15)
[ERROR]     at yargs.parse (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/cli.js:71:45)
[ERROR]     at Object.parse (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/yargs/yargs.js:576:18)
[ERROR]     at /Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/cli.js:49:8
[ERROR]     at Object.<anonymous> (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack-cli/bin/cli.js:366:3)
[ERROR]     at Module._compile (internal/modules/cjs/loader.js:688:30)
[ERROR]     at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
[ERROR]     at Module.load (internal/modules/cjs/loader.js:598:32)
[ERROR]     at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
[ERROR]     at Function.Module._load (internal/modules/cjs/loader.js:529:3)
[ERROR]     at Module.require (internal/modules/cjs/loader.js:636:17)
[ERROR]     at require (internal/modules/cjs/helpers.js:20:18)
[ERROR]     at Object.<anonymous> (/Users/benjamincuthbert/dev/code/rnd/graylog-plugin-pagerduty/node_modules/webpack/bin/webpack.js:156:2)
[ERROR] error Command failed with exit code 1.
[INFO] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Add selectable severity

Any plans to add the option to select the PD severity to be sent for that Graylog alert?

Would be good to be able to route both warning and critical type alerts to the same PD service and have PD handle the escalations appropriately.

As it stands I need to configure more than 1 PD service so I can handle urgent Graylog alerts separately to trivial ones.