Support for PagerDuty v2 key
Albert
shared this idea
-
Ben Morris
commented
+1
I've spent quite a bit of time today trying to get a v2 key working and ended up contacting Mongo support because I was getting inconsistent behaviour in the Atlas UI where I was trying to add a PagerDuty integration with a v2 key. This would work for the test, with a successful alert appearing in PagerDuty, but would fail when saving the integration. It gave the error: "Service Key PagerDuty service key must consist of 32 hexadecimal digits"
I've been advised by Claudio in Mongo support that PagerDuty v2 keys are not supported they pointed me at this ticket. I don't think the documentation is clear that v2 keys aren't supported:
https://www.mongodb.com/docs/atlas/tutorial/pagerduty-integration/#prerequisites just says "All new PagerDuty keys use their Events API v2. If you have an Events API v1 key, you can continue to use that key with Atlas." It could be clearer to explicitly say v2 isn't supported.
UPDATE (Workaround): For my use case, the older Events API v1 was sufficient so I was able to add in an Events API v1 service integration in PagerDuty and then use this in the Atlas alert settings with the PagerDuty alert type.
-
david
commented
The pager duty integration for opsmanager should support pager duty events v2, so the Event Rules can be used in Pager Duty.