-
Type:
Bug
-
Resolution: Done
-
Priority:
Blocker - P1
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: https://docs.opsmanager.mongodb.com/current/tutorial/manage-alert-configurations/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
*Referrer*: https://docs.opsmanager.mongodb.com/current/search/?query=pagerduty
*Screen Resolution*: 1680 x 1050
*Location*: https://docs.opsmanager.mongodb.com/current/tutorial/manage-alert-configurations/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 *Referrer*: https://docs.opsmanager.mongodb.com/current/search/?query=pagerduty *Screen Resolution*: 1680 x 1050
-
0.25
For PagerDuty, only alerts that require acknowledgement can use this delivery method. If the alert is informational only, such as Primary changing in a replica set, PagerDuty will not be selectable on the Alerts configuration page.
- links to