Skip to content

Commit

Permalink
Merge branch 'develop' into NR-352200-managing-session-replay-modify-…
Browse files Browse the repository at this point in the history
…capabilities
  • Loading branch information
adutta-newrelic committed Jan 10, 2025
2 parents c18c4e9 + 3edbf43 commit 77dd887
Show file tree
Hide file tree
Showing 77 changed files with 2,533 additions and 2,583 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,176 @@
---
title: New Relic webhook for Microsoft Teams workflow
tags:
- Alerts
- Incident intelligence
- New Relic webhook for Microsoft Teams workflow
metaDescription: "Read about how to add a New Relic webhook for Microsoft Teams workflow."
freshnessValidatedDate: never
---

Microsoft is retiring Microsoft 365 webhook-based Connectors service in Teams by the end of 2025. To continue receiving New Relic alert notifications, you can create a workflow within Microsoft Teams using the Workflows app. This document provides instructions for updating your New Relic alert destinations and workflows to ensure a smooth transition and uninterrupted alerts in your Teams channels. For more information about retiring the Office 365 Connectors services, refer [Microsoft developer blog](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/).



**Prerequisites:**

* Create a new workflow in Microsoft Teams for New Relic alerts. After creating the workflow, copy the POST request URL. You will need this URL in New Relic. For more information, refer to [Microsoft's documentation to create workflows in Teams](https://support.microsoft.com/en-us/office/create-incoming-webhooks-with-workflows-for-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498).


**To add a New Relic webhook for Microsoft Teams workflow:**


1. Update existing webhook destination:
1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Enrich and Notify > Destinations**.
2. Click the required webhook destination linked to Microsoft Teams to edit.
3. After creating workflows in Teams, in the **Endpoint URL** field, replace the existing URL with a new URL.
<img
title="Destinations update page"
alt="Destinations update page."
src="/images/alerts_destination_enpointurl.webp"
/>
4. Click **Update destination**.
2. Update existing webhook workflow:
1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Enrich and Notify > Workflows**.
2. To edit the notification payload, click the required workflow linked with the destination.
<img
title="Workflow update page"
alt="Workflow update page."
src="/images/alerts_workflow_payload.webp"
/>
3. On the <dnt>Edit notification message</dnt> screen, in the **Template** field, copy and paste the following payload:
```json
{
"type": "message",
"attachments": [
{
"contentType": "application/vnd.microsoft.card.adaptive",
"contentUrl": null,
"content": {
"$schema": "https://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.2",
"body": [
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"items": [
{
"type": "Image",
"style": "Person",
"url": "https://avatars.slack-edge.com/2022-06-02/3611814361970_f6a28959c2e7258660ea_512.png",
"size": "medium"
}
],
"width": "auto"
},
{
"type": "Column",
"items": [
{
"type": "TextBlock",
"size": "large",
"weight": "bolder",
"text": "{{ priorityText }} priority issue is {{#if issueClosedAt}}CLOSED{{else}}{{#if issueAcknowledgedAt}}ACKNOWLEDGED{{else}}ACTIVATED{{/if}}{{/if}}"
},
{
"type": "TextBlock",
"size": "large",
"wrap": "true",
"maxLines": "2",
"weight": "bolder",
"text": "[{{ issueTitle }}]({{ issuePageUrl }})"
}
],
"width": "stretch"
}
]
},
{{#if accumulations.conditionDescription.[0]}}
{
"type": "TextBlock",
"text": {{ json accumulations.conditionDescription.[0] }},
"wrap": true
},
{{/if}}
{{#eq "Not Available" violationChartUrl}}
{{else}}
{
"type": "Image",
"url": {{ json violationChartUrl }}
},
{{/eq}}
{
"type": "FactSet",
"facts": [
{
"title": "*Impacted entities:*",
"value": "{{#each entitiesData.names}}{{#lt @index 5}}{{this}}{{#unless @last}},{{/unless}}{{/lt}}{{/each}}"
},
{{#if accumulations.policyName }}
{
"title": "*Policy:*",
"value": {{ json accumulations.policyName.[0]}}
},
{{/if}}
{{#if accumulations.conditionName }}
{
"title": "*Condition:*",
"value": {{ json accumulations.conditionName.[0]}}
},
{{#eq impactedEntitiesCount 1}}
{{else}}
{
"title": "*Total Incidents:*",
"value": {{ json impactedEntitiesCount}}
},
{{/eq}}
{{/if}}
{
"title": "Workflow Name:",
"value": {{ json workflowName }}
}
]
},
{
"type": "ActionSet",
"actions": [
{
"type": "Action.OpenUrl",
"title": "📥 Acknowledge",
"url": {{ json issueAckUrl }}
},
{
"type": "Action.OpenUrl",
"title": "✔️ Close",
"url": {{ json issueCloseUrl }}
},
{{#if accumulations.deepLinkUrl}}
{
"type": "Action.OpenUrl",
"title": "🔎 View Query",
"url": {{ json accumulations.deepLinkUrl.[0] }},
"mode": "secondary"
},
{{/if}}
{{#if accumulations.runbookUrl}}
{
"type": "Action.OpenUrl",
"title": "📕 View Runbook",
"url": {{ json accumulations.runbookUrl.[0] }},
"mode": "secondary"
}
{{/if}}
]
}
]
}
}
]
}
}
```
4. Click **Save message**.

Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,6 @@ There are several ways you can install the .NET agent, which means there are sev

If you have other installations, see these install docs for those setups for more context:

* [Azure Web Apps](/docs/apm/agents/net-agent/azure-installation/install-net-agent-azure-web-apps/#site-extention-update)
* Docker: [for Windows](/install/dotnet/?deployment=windowsInstall&docker=yesDocker) | for [Linux](/install/dotnet/?deployment=linux&docker=yesDocker)
* [Nuget](/docs/apm/agents/net-agent/install-guides/install-net-agent-using-nuget)

Expand Down Expand Up @@ -77,7 +76,8 @@ Follow the update instructions for your agent:
>
To update the .NET agent for an Azure Web App using the New Relic Azure site extension follow the installation instructions to:

* Install the latest version of the New Relic Azure site extension, which updates the agent files to the latest version.
* Remove the New Relic Azure site extension, this uninstalls the agent
* Re-install the latest version of the New Relic Azure site extension using [these installation instructions](/install/dotnet/?deployment=azure&azure=azuresiteextension), which installs the latest version of the agent.
* Restart the web app to start the updated agent.
</Collapser>
</CollapserGroup>
Expand Down
Loading

0 comments on commit 77dd887

Please sign in to comment.