AppOptics is a powerful service that allows you to collect and visualize metrics for your critical IT systems. With PagerDuty integration, you can now useAppOptics’ alerts to automatically trigger PagerDuty incidents so that your team can be promptly notified about potential issues with your systems.
The PagerDuty integration is quick and easy to setup, just follow this guide to get yourAppOptics and PagerDuty accounts connected.If you are having trouble completing the installation, please contact us.
Title: Service destination name, for example Pagerduty hook .
Service Key: The Service API Key you copied from the PagerDuty services page (REQUIRED).
Description: A short description of the problem that led to this trigger. This field (or a truncated version) will be used when generating phone calls, SMS messages and alert emails. It will also appear on the incidents tables in the PagerDuty UI (REQUIRED).
Incident Key: Identifies the incident to which this trigger event should be applied. If there’s no open (i.e. unresolved) incident with this key, a new one will be created. If there’s already an open incident with a matching key, this event will be appended to that incident’s log. The event key provides an easy way to de-dup problem reports. If this field isn’t provided, PagerDuty will automatically open a new incident with a unique key (OPTIONAL).
This is easy to do with the current integration. Each PagerDuty service within AppOptics can be tied to a different service API key. You would need to make multiple PagerDuty services within PagerDuty and AppOptics.
AppOptics now supports automatic clearing of triggered incidents. What this means for PagerDuty integrations, is that open incidents for a AppOptics service will be resolved when they receive a clear from the AppOptics UI. Webhook integrations will contain a “clear” attribute in the payload.On AppOptics’ end an alert goes into a triggered state when a metric/source violates an alert’s conditions.When all of the faulted signals return to normal values an alert will clear, and a clear notification will be sent.For threshold conditions, a normal state means that it no longer violates the threshold. For absent conditions, a normal state means that the signals started reporting again after an absence. While in a triggered state, a notification will be sent every re-notify interval until the alert clears. Disabling an alert will clear any triggered state. A new “resolve” button on the alert page can be used to manually clear alerts in a triggered state. When an alert transitions from triggered to cleared, the re-notify timer is reset. Note that alert clearing is only supported for new standalone alerts launched earlier this year.
Please contact us if you’re unable to sort out the difficulty.