| Info |
|---|
PagerDuty Notification integration allows Cloudaware to create and update incidents in your PagerDuty using Outbound Webhooks functionality, map PagerDuty incidents to specific Cloudaware CMDB assets and enrich PagerDuty incidents with CMDB data. |
.png?version=1&modificationDate=1725039514736&cacheVersion=1&api=v2)
To see how Cloudaware seamlessly integrates with PagerDuty in action, request a demo.
| Table of Contents |
|---|
Description
Cloudaware uses workflows to initiate a PagerDuty incident based on specific criteria in your environment and resolve an incident once the said criteria is back to normal (optional).
...
Incident Key Field* is used as a dedup_key. The values of this fieldmust be unique for each PagerDuty incident created. This field will be used by PagerDuty for searching an incident when it is being updated or edited. Leave blank if you are not sure what object field is unique. If Incident Key Field is not specified, CA10__caUuid__c will will be used by default to act as the incident identifier. However, the exact value for this field needs to be specified for every Cloudaware object that incidents are created for: go back to the main menu in your Cloudaware account → Setup → type Objects → select the object → locate the field 'CloudAware UUID' in the list and copy its API Name.
Resolve Time Field* will be used to trigger the button 'Resolve' on an incident in PagerDuty (e.g. CA10__closeDate__c: if this field is not blank, the incident will be resolved). If Resolve Time Field is not specified, incidents won't be resolved and closed automatically in PagerDuty.
Fields List* requires a list of fields that will be transmitted into a description of the incident in PagerDuty:
Use the line break sign \n after each field API Name to list the fields in an incident description in a certain order:
| Use - sign before a field API Name to exclude the field from being listed in an incident description:
where - Id will exclude Record ID field |
*You must type API names of fields in Incident Key Field, Resolve Time Field and Fields List exactly as they are on the object (e.g. CA10__caUuid__c, CA10__disappearanceTime__c, etc). To locate API names of fields on a specific object, go to Setup in the main menu → 'Objects' under the section 'Create' → select the object in question → the section 'Custom Fields & Relationships' → locate the field's API name.
...
6. Fill out your Outbound Message details. Paste the URL copied earlier (https://inbound-dot-cloudaware-vm.appspot.com/inbound-message/pager-duty/{key}) in Endpoint URL.
7. Select Available Fields to be displayed in a PagerDuty incident. Click Save.
...
Ensure that API Name of CloudAware UUID field (e.g. CA10__caUuid__c) matches the API Name used as a value for Incident Key Field in the integration setup form.
8. Review the workflow and click Done.
89. Activate the workflow clicking Activate.
910. Once outbound messages are set up, check your PagerDuty Notification integration in Cloudaware. The green light in 'Status' means that the integration has been successfully enabled successfully. If there is a red light, check API Key and Integration Key used for the integration or contactsupport@cloudaware.com.
...