| Info |
|---|
| Info |
The integration allows Cloudaware to create and update incidents in PagerDuty using Outbound Webhooks outbound webhooks functionality, map PagerDuty incidents to specific Cloudaware CMDB assets, and enrich PagerDuty incidents with CMDB data. |
To see how Cloudaware seamlessly integrates with PagerDuty in action, request a demo.
| Table of Contents |
|---|
Introduction
Cloudaware uses workflows to initiate create a PagerDuty incident based on specific criteria in your environment and resolve an the incident once the said criteria is back to normal (optional).
...
Sample use cases
Create a PagerDuty incident when an inappropriate configuration change is detected.
Create a PagerDuty incident in a specific service when Cloudaware detects a spending or a CloudTrail anomaly.
Update a PagerDuty incident when a critical vulnerability has been remediated.
Event
...
passthrough
Cloudaware users can decorate events from third-party monitoring systems, such as Zabbix, New Relic, Splunk, etc., by sending them to Cloudaware first. Cloudaware may enrich enriches events with details like AWS Account ID or Azure Resource Group and tags , so that further downstream PagerDuty can make more intelligent routing, suppression, and escalation decisions.
...
Set up the integration in Cloudaware
...
Log in to
...
Cloudaware account
...
→ Admin.
Find PagerDuty Notification in Other Integrations. Click +Add.
...
Fill out the form:
...
WHERE
Name - PagerDuty Notification integration name in Cloudaware
API Key - API Key generated in
...
PagerDuty
...
| Note |
|---|
If you have PagerDuty Accounts integration enabledPagerDuty account is added to Cloudaware, copy the API Key used for this integration (check step 2 of check the guide PagerDuty Accounts Integration). |
Integration Key - Integration key can be found in details of the Service you would like to monitor monitored service (in PagerDuty select , go to Service Directory → Service in question → the tab 'Integrations').
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. If Incident Key Field PagerDuty uses this field to search for incidents when updating or editing them. If the Incident Key field is not specified, CA10__caUuid__c 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 |
symbol |
a |
specific order:
|
Prefix a field API Name with a |
it from the incident description:
where |
*You must type 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 find API names of fields on a specific object, go to Setup in the main menu , navigate in Cloudaware to Setup → 'Objects' under the section ' Create' → select the object in question → the section 'Custom Fields & Relationships' → locate the field's API name.
...
.
...
Check the integration details. Copy the Endpoint URL
...
in the format https://inbound-dot-cloudaware-vm.appspot.com/inbound-message/pager-duty/{key}
...
for further configuration.
...
Set up a workflow rule in Cloudaware
The workflow functionality allows to trigger triggers incidents in PagerDuty when certain criteria is met based on specific criteria in Cloudaware.
Create a workflow based on conditions you are interested in rule with defined conditions and add an outbound message that will use using the Endpoint URL copied from details of the PagerDuty Notification integration details. Once When the conditions are met, the rule workflow will trigger PagerDuty to create , creating a new incident against for the monitored service which is being monitored.
Use case: You would like to get Trigger a PagerDuty incident created every time when whenever an AWS EC2 instance status changes. Create To do this, create a workflow rule for the object 'AWS EC2 Instance Status Event' object.
1. Log in to Cloudaware account . Click Setup in the main menu under your username→ Setup.
2. In the Quick Find box start typing workflows to select Workflows & Approvals → Workflow Rules → New Rule:
...
9. Activate the workflow clicking Activate.10. 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. If there is a red light, check API Key and Integration Key used for the integration or contactsupport@cloudaware.com.
...
PagerDuty incident in Cloudaware CMDB
Cloudaware parses PagerDuty incidents, allowing customers to gain visibility of events. Here is a sample PagerDuty incident in Cloudaware:
...