Guidelines
parent
dde26f5fc0
commit
9e26586760
|
|
@ -28,7 +28,7 @@ To monitor your application with Dynatrace, please follow these steps:
|
|||
|
||||
6. (optional) Configure Notification System
|
||||
- Dynatrace AI automatically detects anomalies in your applications and generate problems, visible within the UI. Dynatrace offers several out-of-the-box integrations with problem notification systems such as Email, MS Teams and ITSM.
|
||||
- Notification system is not configured by default. If you want to enable it for your application please follow this [link](link).
|
||||
- Notification system is not configured by default. If you want to enable it for your application please follow this [link](https://atc.bmwgroup.net/bitbucket/projects/OPAPM/repos/cd_e2e_monitoring_config/browse/onboarding/CD_newComponentTag/notification/README.md).
|
||||
7. (optional) Add databases to Management Zone
|
||||
- The script described in step 5 will create the configuration for all entities related to your application (Host, Processes, Services) but not the databases.
|
||||
- To add your databases into Dynatrace you need to add an extra rule to the [Component.json](https://atc.bmwgroup.net/bitbucket/projects/OPAPM/repos/cd_e2e_monitoring_config/browse/BMW-Dynatrace-config/00_Global-Config/auto-tag/Component.json) file. You can use [this](link) example to understand exactly what you have to do.
|
||||
|
|
@ -55,7 +55,7 @@ To monitor your application with Dynatrace, please follow these steps:
|
|||
- You can use the generated MZ clicking on the filter at the top-right corner within the Dynatrace UI.
|
||||
- Learn how to configure/improve your Management Zone [here](link) ([Do i need to configure it?](link))
|
||||
|
||||

|
||||

|
||||
|
||||
- *Dashboards*
|
||||
- Based on a template,
|
||||
|
|
@ -64,7 +64,7 @@ To monitor your application with Dynatrace, please follow these steps:
|
|||
- For PreProd environments, INT dashboard will be generated.
|
||||
- Learn how to configure/improve your Dashboards [here](link) ([Do i need to configure it?](link))
|
||||
|
||||

|
||||

|
||||
|
||||
**Recommended**
|
||||
- Participate in one of the Dynatrace trainings to understand
|
||||
|
|
|
|||
|
|
@ -9,14 +9,21 @@ Follow [this](https://www.dynatrace.com/support/help/shortlink/set-up-msteams-in
|
|||
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"`
|
||||
|
||||
`- 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 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:
|
||||
|
|
@ -26,17 +33,25 @@ 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"`
|
||||
|
||||
`- 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`
|
||||
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`
|
||||
|
||||
### ITSM
|
||||
|
|
|
|||
Loading…
Reference in New Issue