starred/healthchecks

Fork 0

mirror of https://github.com/healthchecks/healthchecks.git synced 2026-04-25 15:05:49 +03:00

[GH-ISSUE #303] Where do I get PD_VENDOR_KEY ? #229

New issue

Closed

opened 2026-02-25 23:41:41 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 23:41:41 +03:00

Owner

Originally created by @gsiddardha on GitHub (Nov 21, 2019).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/303

Hi,

I'm trying to setup healthchecks on my system with PD integration. This requires PD_VENDOR_KEY value to be set. I am not able to find any documentation on pagerduty website on how to get this value. Can someone please help point me to the right documentation?

Originally created by @gsiddardha on GitHub (Nov 21, 2019). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/303 Hi, I'm trying to setup healthchecks on my system with PD integration. This requires PD_VENDOR_KEY value to be set. I am not able to find any documentation on pagerduty website on how to get this value. Can someone please help point me to the right documentation?

kerem closed this issue

2026-02-25 23:41:41 +03:00

kerem commented

2026-02-25 23:41:42 +03:00

Author

Owner

@cuu508 commented on GitHub (Nov 21, 2019):

PD_VENDOR_KEY is needed for PagerDuty Connect, a mechanism for authorizing an integration to access user's PagerDuty account.

From https://www.pagerduty.com/docs/guides/pagerduty-connect/

vendor: A unique identifier for the partner. Please contact support for your vendor key.

I got my vendor key after filling out a "Become a Partner" form somewhere on their site (this was a while ago, not sure if the process would be the same now).

For private self-hosted installations becoming a partner might not be feasible, but it should be possible to use PagerDuty API without using PagerDuty Connect. In fact, this is how the integration used to work before I implemented PagerDuty Connect here:

github.com/healthchecks/healthchecks@96e00df0ab

Ideally Healthchecks would use the old way if PD_VENDOR_KEY is not set, and PagerDuty Connect if PD_VENDOR_KEY is set.

@cuu508 commented on GitHub (Nov 21, 2019): PD_VENDOR_KEY is needed for PagerDuty Connect, a mechanism for authorizing an integration to access user's PagerDuty account. From https://www.pagerduty.com/docs/guides/pagerduty-connect/ > vendor: A unique identifier for the partner. Please contact support for your vendor key. I got my vendor key after filling out a "Become a Partner" form somewhere on their site (this was a while ago, not sure if the process would be the same now). For private self-hosted installations becoming a partner might not be feasible, but it should be possible to use PagerDuty API without using PagerDuty Connect. In fact, this is how the integration used to work before I implemented PagerDuty Connect here: https://github.com/healthchecks/healthchecks/commit/96e00df0ab4c330b40b74c7c8fbe3c8668f9e38f Ideally Healthchecks would use the old way if PD_VENDOR_KEY is not set, and PagerDuty Connect if PD_VENDOR_KEY *is* set.

kerem commented

2026-02-25 23:41:42 +03:00

Author

Owner

@gsiddardha commented on GitHub (Nov 21, 2019):

Got it.

Currently healthchecks also has a restriction on the key to be non-null, to allow PD integration.

I guess I can manually add a Channel entry with kind = pd as a hack for now. Please correct me if I'm wrong.

@gsiddardha commented on GitHub (Nov 21, 2019): Got it. Currently healthchecks also has a restriction on the key to be non-null, to allow PD integration. 1. [Enable PD integration only if `enable_pd`](https://github.com/healthchecks/healthchecks/blob/master/templates/front/channels.html#L254) 2. [Set `enable_pd` to `false` if `PD_VENDOR_KEY` is None](https://github.com/healthchecks/healthchecks/blob/master/hc/front/views.py#L255) I guess I can manually add a Channel entry with `kind` = pd as a hack for now. Please correct me if I'm wrong.

kerem commented

2026-02-25 23:41:42 +03:00

Author

Owner

@cuu508 commented on GitHub (Nov 21, 2019):

Ah yes, that would be a clever workaround for time being. When creating the Channel, the value field needs to look like so:

{"service_key": "api key here", "account": "name of the account for display"}

@cuu508 commented on GitHub (Nov 21, 2019): Ah yes, that would be a clever workaround for time being. When creating the Channel, the value field needs to look like so: `{"service_key": "api key here", "account": "name of the account for display"}`

kerem commented

2026-02-25 23:41:42 +03:00

Author

Owner

@gsiddardha commented on GitHub (Nov 21, 2019):

cool. got it working. thanks for the support.

Any thoughts on how we can manage this better? instead of manually adding a channel for each new project.

@gsiddardha commented on GitHub (Nov 21, 2019): cool. got it working. thanks for the support. Any thoughts on how we can manage this better? instead of manually adding a channel for each new project.

kerem commented

2026-02-25 23:41:42 +03:00

Author

Owner

@cuu508 commented on GitHub (Nov 22, 2019):

Any thoughts on how we can manage this better? instead of manually adding a channel for each new project.

I'm working on supporting both the old onboarding flow where the user supplies an API key, and the PagerDuty Connect one (if PD_VENDOR_KEY is set).

@cuu508 commented on GitHub (Nov 22, 2019): > Any thoughts on how we can manage this better? instead of manually adding a channel for each new project. I'm working on supporting both the old onboarding flow where the user supplies an API key, and the PagerDuty Connect one (if PD_VENDOR_KEY is set).

kerem commented

2026-02-25 23:41:42 +03:00

Author

Owner

@cuu508 commented on GitHub (Nov 22, 2019):

This is now implemented – you can now add a PagerDuty integration without having the PD_VENDOR_KEY set.

@cuu508 commented on GitHub (Nov 22, 2019): This is now implemented – you can now add a PagerDuty integration without having the `PD_VENDOR_KEY` set.

kerem referenced this issue

2026-02-25 23:44:08 +03:00

[PR #229] [MERGED] Add Pager Team integration #918