FR: Pagerduty integration URL override

[jinnatar]

Describe the feature request

Allow overriding the endpoint URL of the PagerDuty alerting integration so that one can point directly to the correct region of PagerDuty. Currently the endpoint is hardcoded at

gatus/alerting/provider/pagerduty/pagerduty.go

Line 17 in 2fe9913

restAPIURL = "https://events.pagerduty.com/v2/enqueue"

which means all traffic will transit through their US region.

There doesn't seem to be an existing consensus for this config key name from my sampling, but PagerDuty call it themselves "integration URL", which matches the current integration-key field naming, so I suggest integration-url as the config key.

Why do you personally want this feature to be implemented?

Pageduty themselves now warn when creating an integration that:

To prevent your event traffic from being proxied through the United States, always provide 3rd party integrations with the full integration URL, when supported.

In my case thus I should override the endpoint URL to https://events.eu.pagerduty.com/v2/enqueue to gain (presumably) faster latency, perhaps a bit of resiliency and data sovereignty.

How long have you been using this project?

2y

Additional information

No response