New Relic

purpose echoes can connect to your new relic account and monitor your incidents lifecycle in order to produce some metrics such as the mean time to recovery docid\ lgfiztdecxm2tq2kurlip installation new relic integration is done through the integrations settings the installation will guide you into generating a user api key make sure to select the appropriate region once the connection is made you will be invited to select the new relic account on which to install echoes echoes will then install a destination (webhook) on the selected new relic account setting up your new relic workflow the next step is to setup a new relic workflow in order to send incidents' events to echoes through the destination previously set during the installation the destination to be selected is echoes webhook requirements on the message template the only requirement expected from echoes is that the message template includes the issueid i e { "id" {{ json issueid }} } reference an echoes team as owner of a service 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 serviceownerteamid is to be set in the notification payload { "id" {{ json issueid }}, "serviceownerteamid" "cbdf76fc 3015 4c66 a5f8 143a48734e48" } the team id value itself could be held by a specific tag when setting up the new relic workflow this tag could then be referenced in the template to be loaded dynamically when constructing the notification payload how to get the correct team id from echoes? the team ids can be found by using our teams api