Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14707

[O/CM] clarify pagerduty api key usage

      Description

      In the docs for

      There's a note:

      PagerDuty decommissioned their v1 API key in October 2018. If you have a v1 key, you can continue to use that key with Atlas. All new PagerDuty keys use their v2 API, but Atlas does not support their v2 key. If you don't have their v1 key, use Webhook instead of PagerDuty.

      However this is slightly misleading. Please change the note to reflect that the REST API v1 was decommissioned. Our monitoring integrations work just fine with PagerDuty's Events API v1. PD prioritizes the Events API V2, they will need to search for the Events API v1 manually.

      My proposed change for the note is:

      PagerDuty decommissioned their REST API v1 key in October 2018. If you have a v1 key, you can continue to use that key with Atlas. All new PagerDuty keys use their REST API v2, but Atlas does not support those v2 keys. If you don't have their REST API v1 key, please use the PagerDuty Events API v1 integration key instead.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            corry.root@mongodb.com Corry Root
            Reporter:
            corry.root@mongodb.com Corry Root
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              2 years, 43 weeks, 1 day ago