I’m trying to add PagerDuty integration to our LibreNMS instance but failing miserably. I click on the gear icon, go to alerting settings, click on the PagerDuty transport section and click on the “Alert with PagerDuty” button and get taken to a 404 error page on PagerDuty’s site. When I hover over the button the link shows https://connect.pagerduty.com/connect?vendor=2fc7c9f3c8030e74aae6&callback=%2F%2F%2Fsettings%2Fsub%3Dalerting%2F%2F which almost looks like it’s trying to pull an old configuration from somewhere. Any thoughts on what I might be doing wrong or what to do next?
Hello,
nrcbhermsen
run from cli ./validate.php and post the return.
==========================================================
| Component | Version |
|---|---|
| LibreNMS | 3dd6628101acf51790337c07d96c8e7a2be1ad01 |
| DB Schema | 194 |
| PHP | 7.0.19 |
| MySQL | 5.5.52-MariaDB |
| RRDTool | 1.4.8 |
| SNMP | NET-SNMP 5.7.2 |
==========================================================
[OK] Database connection successful
[FAIL] Database: incorrect column (dbSchema/version)
[FAIL] Database: missing index (dbSchema/PRIMARY)
[FAIL] Database: missing column (users/remember_token)
[FAIL] Database: missing column (users/updated_at)
[FAIL] We have detected that your database schema may be wrong, please report the following to us on IRC or the community site (https://t.libren.ms/5gscd):
ALTER TABLE dbSchema CHANGE version version int(11) NOT NULL DEFAULT ‘0’;
ALTER TABLE dbSchema ADD PRIMARY KEY (version);
ALTER TABLE users ADD remember_token varchar(100) NULL AFTER realname;
ALTER TABLE users ADD updated_at timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP AFTER remember_token;
[FAIL] Some devices have not completed their polling run in 5 minutes, this will create gaps in data.
Check your poll log and refer to http://docs.librenms.org/Support/Performance/
nsvpx2.nationalresearch.com
I’m guessing PD may have changed the way integration works.
nrcbhermsen,
you still need to fix those [FAIL]
The unfortunate part of that would be is their whole instructions for enabling PagerDuty with LibreNMS is go click on the button in LibreNMS and then log in. 
Validate looks much better now 
bash-4.2$ ./validate.php
| Component | Version |
|---|---|
| LibreNMS | 5c58cc011ad5fa8a47f7242ce4cf2df317726a96 |
| DB Schema | 194 |
| PHP | 7.0.19 |
| MySQL | 5.5.52-MariaDB |
| RRDTool | 1.4.8 |
| SNMP | NET-SNMP 5.7.2 |
==========================================================
[OK] Database connection successful
[OK] Database schema correct
nrcbhermsen,
is pager duty working now?.. I just tried mine and worked fine the link takes me the pager duty page.
Nope still getting the 404 error:
With the address of: https://connect.pagerduty.com/connect?vendor=2fc7c9f3c8030e74aae6&callback=%2F%2F%2Fsettings%2Fsub%3Dalerting%2F%2F
Here’s what i get https://connect.pagerduty.com/connect?vendor=2fc7c9f3c8030e74aae6&callback=http%3A%2F%2Fnms.nbisd.edu%2F%2F%2Fsettings%2Fsub%3Dalerting%2F%2F
what Version of LibreNMS are you on?
Settings>About
Looking at what you’re getting vs what I’m getting I appear to be missing some of the callback part of the URL.
And found it:
$config['base_url'] = '/';
was messing things up.
1 Like
I’m glad you got it figured out 
I’m still having this issue. Getting a 404 when clicking on the button.
There might be some sort of configuration issue within PD’s side. The current alert transport is using wrong URLs but even after changing them the simple install flow does not work.
However, you can create the integration keys manually in PD and paste them to the transport config. That works with both regions. I created a support ticket on PD for this issue just a few minutes ago ;).
Yes, PagerDuty support gave me this info too, it’s working now.
(Under Services/Service Directory/New Service you can do this manually)