guidelines / templates redefined
parent
c5c4adad8b
commit
96b2cdb25c
|
|
@ -8,23 +8,21 @@ https://empty webhook (not configured).
|
|||
Follow [this](https://www.dynatrace.com/support/help/shortlink/set-up-msteams-integration#configuration-in-microsoft-teams) link
|
||||
3. Add the incoming webhook to this line:
|
||||
|
||||
`<app_name>-PROD.EMEA-Prod:`
|
||||
|
||||
`- name: CD_<app_name> PROD`
|
||||
|
||||
`- alertingProfile: CD_<app_name>/alerting-profile/CD<app_name>-PROD.id`
|
||||
|
||||
`- webhook: <here>`
|
||||
|
||||
`- skipDeployment: "false"`
|
||||
```
|
||||
<app_name>-PROD.EMEA-Prod:
|
||||
- name: CD_<app_name> PROD
|
||||
- alertingProfile: CD_<app_name>/alerting-profile/CD<app_name>-PROD.id
|
||||
- webhook: <here>
|
||||
- skipDeployment: "false"
|
||||
```
|
||||
|
||||
4. Save and commit changes:
|
||||
|
||||
`git add <changes>`
|
||||
|
||||
`git commit -m "<app_name> configuration changes"`
|
||||
|
||||
`git push -u origin <branch>`
|
||||
```
|
||||
git add <changes>
|
||||
git commit -m "<app_name> configuration changes"
|
||||
git push -u origin <branch>
|
||||
```
|
||||
|
||||
Note: If you want to enable MS Teams for any other hub/stage, follow the same steps but make sure you're under the right configuration:
|
||||
`<app_name>-<stage>.<env>-<stage>:`
|
||||
|
|
@ -33,31 +31,29 @@ Note: If you want to enable MS Teams for any other hub/stage, follow the same st
|
|||
In the following example, the team intends to use email instead of the default one (MS Teams) for the EMEA PROD notification system. For that, the following changes have to be done:
|
||||
1. Keep the MS Teams integration disabled, with the https://empty webhook
|
||||
|
||||
`<app_name>-PROD.EMEA-Prod:`
|
||||
|
||||
`- name: CD_<app_name> PROD`
|
||||
|
||||
`- alertingProfile: CD_<app_name>/alerting-profile/CD<app_name>-PROD.id`
|
||||
|
||||
`- webhook: https://empty`
|
||||
|
||||
`- skipDeployment: "false"`
|
||||
```
|
||||
<app_name>-PROD.EMEA-Prod:
|
||||
- name: CD_<app_name> PROD
|
||||
- alertingProfile: CD_<app_name>/alerting-profile/CD<app_name>-PROD.id
|
||||
- webhook: https://empty
|
||||
- skipDeployment: "false"
|
||||
```
|
||||
|
||||
2. Create a new configuration template under config, using the email template:
|
||||
|
||||
`config:`
|
||||
|
||||
`- CD<app_name>email: email.json`
|
||||
```
|
||||
config:
|
||||
- CD<app_name>email: email.json
|
||||
```
|
||||
|
||||
3. Describe the configuration below, using the following template:
|
||||
|
||||
`CD<app_name>email.EMEA-Prod:`
|
||||
|
||||
`- name: CD_<app_name> PROD`
|
||||
|
||||
`- alertingProfile: CD_<app_name>/alerting-profile/CD<app_name>-PROD.id`
|
||||
|
||||
`- receivers: distributionEmailexample@bmw.de`
|
||||
```
|
||||
CD<app_name>email.EMEA-Prod:
|
||||
- name: CD_<app_name> PROD
|
||||
- alertingProfile: CD_<app_name>/alerting-profile/CD<app_name>-PROD.id
|
||||
- receivers: distributionEmailexample@bmw.de`
|
||||
```
|
||||
|
||||
### ITSM
|
||||
Coming soon!
|
||||
Loading…
Reference in New Issue