Datadog

purpose echoes can connect to your datadog account and monitor your incidents lifecycle in order to produce some metrics such as the mean time to recovery docid\ lgfiztdecxm2tq2kurlip installation datadog integration is done through the integrations settings the installation will guide you into generating an organization’s api key and an application key for the application key we encourage to create a service account as key holder make sure to select the appropriate site once the connection is made you will be invited to select the datadog organization on which to install echoes echoes will then install a webhook integration on the selected datadog organization required permissions it is advised to create a custom role specific to echoes and associate the role to the user the application key has been issued for echoes custom role the following permissions are required for echoes to interact with datadog integration manage service catalog read setting up your datadog incident notification rule the next step is to setup an incident notification rule in order to send incidents' events to echoes through the webhook previously set during the installation the destination to be selected is echoes webhook configure the events to be sent if state is to change or echoes teamid (optional) reference an echoes team as owner of a service (optional) a service may represent an application, a component, to open incidents against in order to associate a service suffering an incident to a team in echoes, the property echoes teamid is to be added to the incident's property fields as a custom field this field is not mandatory add custom field it is to be defined as a text area and a user input custom field attributes the team id value itself can then be set via the incident attributes on the incident page how to get the correct team id from echoes? the team ids can be found by using our teams api