[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: |
|
|||||||||||||||
| Issue Links: |
|
|||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||
| Participants: | ||||||||||||||||
| Days since reply: | 2 years, 27 weeks ago | |||||||||||||||
| Description |
DescriptionIn the docs for
There's a note:
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:
Scope of changesImpact to Other DocsMVP (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: (
|
| Comment by Githook User [ 04/Aug/21 ] |
|
Author: {'name': 'corryroot', 'email': '72401712+corryroot@users.noreply.github.com', 'username': 'corryroot'}Message: (
|
| Comment by Corry Root [ 04/Aug/21 ] |
|
amit.jain, I updated the PagerDuty note on the following page. |