Unexpected behavior of using downloaded configs between environments : Deploy creates duplicate entries for dashboard and alerting profiles #241
Unanswered
avwsolutions
asked this question in
Archive
Replies: 2 comments 4 replies
-
Hi, Could you please share the dashboard json and alerting profile jsons which cause this behavior? |
Beta Was this translation helpful? Give feedback.
0 replies
-
@avwsolutions duplicated objects are usually created if monaco is not able to find existing object with the same name. As @patrickpichler suggested, please share JSONs with us so we can have a look. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi All,
We (me and @AH-ErikPost ) are busy with a migration from Managed Dynatrace (PRD) to Dynatrace SAAS (DTA). We are using Monaco to download the configuration from our managed tenants and apply it to our SAAS DTA. What we currently see is that the dry-run goes well, but actually the deployments created the objects, but after a re-run the same object is created again (so duplicates). We observed this behaviour for dashboards and alerting profiles.
When we directly download the project from the target SAAS DTA (deploy) environment this behavior is not there anymore and we can see that only one object is maintained.
The questions arise now how we can use Monaco as a tool for our pipeline automation (Github actions).
Our goal is to have multiple versions configurations that can both imported in DTA and PRD without created duplicate objects. So we can have configuration made once and applied multiple times at different environments/tenants.
please advice in this one. We are using the latest monaco release with CLI 2.0 options enabled.
Beta Was this translation helpful? Give feedback.
All reactions