Once you have Configured a PagerDuty Integration within Cyara, this article outlines a typical workflow of how to use the integration effectively.

The Cyara-PagerDuty integration can be configured using two different methods, Automatic or Manual Ticket Creation, see below for details.

Manual Incident Ticket Creation

When you configure your PagerDuty integration, by default it will be setup to only create incident tickets manually. This process works as follows.

• A Test Case is run, either within a campaign or on it's own.
• This Test Case returns a result.
• From the result, an option is available to create a PagerDuty incident ticket.
  Click the Create button for Ticket in the Actions sidebar.
  
• Cyara will prefill configured fields, but you can still make manual changes if need be. Click Create to send the Incident Ticket to PagerDuty. 
  
• Once the Incident Ticket has been created, a link will appear on the Test Case Result in Cyara that links to the Incident within PagerDuty.
  
• Clicking this link will take you directly to the Incident Ticket within PagerDuty.
  

Automatic Incident Ticket Creation

The Cyara-PagerDuty integration also allows for incidents to be created automatically once configured. This system works on the "Failure Threshold" value, which is the number of concurrent Test Case failures that must happen in order for an incident ticket to be created.

This Failure Threshold value is set on a Service Group for the Pulse Dashboard being used. Service Groups define what is displayed on the Dashboard, using the generic or customized categories.

After the parameters for the Pulse Dashboard are defined, Dashboard Administrators need to configure one or more service (categories and groups) before any results can be aggregated and shown on the Dashboard.

A Service Group can represent the test results either in tabular form or real-time charts. To setup a Service Group follow the steps below.

1. Log in to the Cyara Portal as an Dashboard Admin user.
2. From the main menu, click the Reports option and then choose Dashboard Configuration from the Pulse section.
   
3. Click the Edit button against the Dashboard for which you want to create a new Service Group. A screen as shown below appears:
   
4. To create a new Service Group, click the New Group button, and a screen as shown appears:
   
5. The Failed Threshold Value is what determines when a PagerDuty Incident Ticket is automatically created. A Failed Threshold of 3 for example will wait for 3 concurrent Test Case failures to occur within a Pulse Campaign before automatically creating an incident ticket with the details of the 3rd Test Case failure.

Automatically Closing Created Incident Tickets

Note: This feature is only available if you are using the Automatic Incident Ticket Creation process as described above.

In addition to having tickets be created automatically, Cyara can now automatically resolve this type of ticket using the new Success Threshold value. This value works by looking for a concurrent number of Test Case successes, once this value has been reached the last automatically created ticket will be marked as Resolved.

To Configure the Success Threshold value to automatically resolve PagerDuty Incident Tickets that were automatically created, follow the steps below.

1. Log in to the Cyara Portal as an Dashboard Admin user.
2. From the main menu, click the Reports option and then choose Alarm Profiles from the Pulse section, then click on the Email & Web Hook tab.
3. Ensure the Alert By Integration checkbox is ticked and that the correct integration is selected in the available drop down menu.
4. Set the Success Threshold value and click Save Details.
5. After an alert is triggered a clearing alert is sent after the next successful run. This threshold allows you to configure the number of continuous successful runs before sending a clearing alert.