diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 9227daf2a3f87..9880372798dfa 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -2378,16 +2378,21 @@ menu: parent: oncall identifier: oncall_schedules weight: 5 + - name: Automations + url: service_management/on-call/automations + parent: oncall + identifier: oncall_automations + weight: 6 - name: Profile Settings url: service_management/on-call/profile_settings/ parent: oncall identifier: oncall_profile_settings - weight: 6 + weight: 7 - name: Guides url: service_management/on-call/guides/ parent: oncall identifier: oncall_guides - weight: 7 + weight: 8 - name: Event Management url: service_management/events/ pre: events diff --git a/content/en/service_management/on-call/automations.md b/content/en/service_management/on-call/automations.md new file mode 100644 index 0000000000000..3afc8bb96a5e0 --- /dev/null +++ b/content/en/service_management/on-call/automations.md @@ -0,0 +1,44 @@ +--- +title: Automations +further_reading: +- link: '/service_management/on-call/' + tag: 'Documentation' + text: 'Datadog On-Call' +- link: "https://docs.datadoghq.com/service_management/workflows/" + tag: "Documentation" + text: "Workflow Automation" +--- + +## Overview + +Automations allow you to trigger actions based on events in On-Call. There are two types: +- **Handover automations**: Triggered automatically when an on-call shift changes. +- **[Workflow automations][1]**: A low-code/no-code solution that lets you define actions based on various on-call activities. + + +## Handover automations +Handover automations run automatically at the start or end of an on-call shift. They're designed to handle tasks that teams typically manage with custom scripts—such as notifying other systems about who's on-call, updating internal dashboards, or rotating credentials. + +By using built-in automations instead of maintaining cron jobs or custom tools, you can streamline operations, eliminate manual steps, and ensure the right actions always run when a shift changes. + + +
+If you need a specific action that isn't listed, contact your account representative or support@datadoghq.com. +
+ +Handover Automations are maintained on a Team level. To get started, navigate to [On-Call Team][4], open a specific team, and scroll down to the **Handover Automation** section. + +### Send a Slack message +Post a message to Slack at the start or end of a shift using a handover automation. The message shows the previous and next on-call users (if any). **Note**: This requires the Datadog Slack app—make sure it's [added to your workspace][2]. + +### Send a Microsoft Teams message +Post a message to Microsoft Teams at the start or end of a shift using a handover automation. The message shows the previous and next on-call users (if any). **Note**: This requires the Datadog Teams app—make sure it's [added to your workspace][3]. + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} + +[1]: /service_management/workflows/ +[2]: /integrations/slack/?tab=datadogforslack#install-the-datadog-app-in-your-slack-workspace +[3]: /integrations/microsoft_teams/?tab=datadogapprecommended#overview +[4]: https://app.datadoghq.com/on-call/teams