Pagerduty alert transport throws error 400 - Bad request: Invalid routing key

[fth]

Hi!

I have had a working PagerDuty altert transport but somewhere along the line it stopped working. So I started digging in it today, but can’t find the solution. So I thought I’ll ask here for some help.

This is the error I receive when testing the alert transport is:

Test to pagerduty failed
Request to PagerDuty API failed. Client error: POST https://events.eu.pagerduty.com/v2/enqueue resulted in a 400 Bad Request response: Invalid routing key

I’ve created a new API key with the same result (@PagerDuty web site: Integrations → API Access keys).

Any thoughts?

Output from validate.php:

$ /opt/librenms/validate.php

Component	Version
LibreNMS	22.6.0-2-g1056f28de
DB Schema	2022_05_30_084932_update-app-status-length (242)
PHP	7.3.33
Python	3.6.8
MySQL	10.5.15-MariaDB
RRDTool	1.4.8
SNMP	5.7.2

====================================

[OK] Composer Version: 2.3.7
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database Schema is current
[OK] SQL Server meets minimum requirements
[OK] lower_case_table_names is enabled
[OK] MySQL engine is optimal
[OK]
[OK] Database schema correct
[OK] MySQl and PHP time match
[OK] rrd_dir is writable
[OK] rrdtool version ok

[fth]

Did notice that my previous integration was made through PagerDuty → SERVICE DIRECTORY
OPERATIONS, SERVERS, NETWORK, WEB INTEGRATIONS. But when using this method I just get another error message:

Test to pagerduty failed
Request to PagerDuty API failed. Client error: POST https://events.pagerduty.com/generic/2010-04-15/create_event.json resulted in a 400 Bad Request response: {“status”:“unrecognized object”,“message”:“Event object format is unrecognized”,“errors”:[“JSON parse error”]}