[DOCS-14707] [O/CM] clarify pagerduty api key usage Created: 04/Aug/21  Updated: 04/Aug/21  Resolved: 04/Aug/21

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Corry Root Assignee: Corry Root
Resolution: Done Votes: 0
Labels: integrations
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File image-2021-06-11-16-59-47-891.png    
Issue Links:
Cloners
clones DOCS-14559 [Atlas] clarify pagerduty api key usage Closed
Related
Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-14710 [OM] Backport DOCS-14707 to v5.0 Backport Sub-Task Closed Corry Root  
DOCS-14711 [OM] Backport DOCS-14707 to v4.4 Backport Sub-Task Closed Corry Root  
Participants:
Days since reply: 2 years, 27 weeks ago

 Description   

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.)



 Comments   
Comment by Githook User [ 04/Aug/21 ]

Author:

{'name': 'corryroot', 'email': '72401712+corryroot@users.noreply.github.com', 'username': 'corryroot'}

Message: (DOCS-14711): Backport DOCS-14707 to v4.4. (#3915)

  • (DOCSP-14707) Updated PagerDuty note.
Comment by Githook User [ 04/Aug/21 ]

Author:

{'name': 'corryroot', 'email': '72401712+corryroot@users.noreply.github.com', 'username': 'corryroot'}

Message: (DOCS-14710): Backport DOCS-14707 to v5.0. (#3915)

  • (DOCSP-14707) Updated PagerDuty note.
Comment by Corry Root [ 04/Aug/21 ]

amit.jain, I updated the PagerDuty note on the following page.

OM STAGE

CM STAGE

BUILD

Generated at Thu Feb 08 08:11:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.