Versions Compared

Version Old Version 35 New Version Current
Changes made by

Daria Lebedeva

Daria Lebedeva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cloudaware uses workflows to create a PagerDuty incident based on specific criteria and resolve the incident once the said criteria is back to normal (optional).Image Removed

...

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 can decorate events from third-party monitoring systems, such as Zabbix, New Relic, Splunk, etc., by sending them to Cloudaware first. Cloudaware enriches events with details like AWS Account ID or Azure Resource Group and tags so that PagerDuty can make more intelligent routing, suppression, and escalation decisions.

...

Integration Key - Integration key of the monitored service (in PagerDuty, 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. 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 \n after each field API Name to list the incident fields in a specific order:

Code Block
CA10__subject__c\n
CA10__closeDate__c\n
CA10__status__c\n
CA10__description__c\n

Prefix a field API Name with a - to exclude it from the incident description:

Code Block
CA10__subject__c\n
- Id

where - Id will exclude the field Record ID

...

9. Activate the workflow clicking Activate.10. To view

PagerDuty incident in Cloudaware CMDB

Cloudaware parses PagerDuty incidents, go to Cloudaware CMDB Navigator. Select PAGERDUTY in the menu on the left → PagerDuty Incidents.allowing customers to gain visibility of events. Here is a sample PagerDuty incident in Cloudaware:

...