itsjohannawren / pd-nag-connector Goto Github PK

I've got everything configured in Nagios per the README, and I can see that Nagios is calling pagerduty.pl, but PagerDuty shows no new incidents.

As a test, I've tried using a wrapper script on the plugin to capture stderr and the exit code (http://www.waggy.at/nagios/capture_plugin.htm). The output is blank with exit code "0", so I assume that the API call is succeeding.

Running pagerduty.pl manually:

$ sudo -u nagios /usr/bin/env perl /usr/local/nagios/plugins/pagerduty.pl; echo $?
Use of uninitialized value in string eq at /usr/local/nagios/plugins/pagerduty.pl line 181.
Use of uninitialized value in string eq at /usr/local/nagios/plugins/pagerduty.pl line 197.
Use of uninitialized value in string eq at /usr/local/nagios/plugins/pagerduty.pl line 197.
Use of uninitialized value in string eq at /usr/local/nagios/plugins/pagerduty.pl line 197.
0

No obvious errors here other than missing environment variables, I believe.

Short of adding my own, is there any way to get verbose/debugging output?

Jeff,

Since David added support for Icinga, should we call this out more explicitly in the title and description?

-Chris

Request: Modify the script so that it's set up to work with services of type Nagios, not Generic API. https://github.com/jeffwalter/pd-nag-connector/blob/master/pagerduty.cgi this script that interprets our webhooks would need to be modified to handle the Nagios service type.

Can this log errors to syslog instead of stdout? This may make tracking down errors easier.