Monaco 2.0 is not downloading Management Zones

[tfaqir-observe]

Hi 

We are running Monaco 2.0 running against managed tenant version 1.270.96.20230711-145538. I'm able to download all Dynatrace Config entities like Dashboards, SLO, synthetic-monitor etc. except for management zones. Even the management zone folder doesn't get created. No related error message pops up. Here is the only error message I get and it's not related to Management Zones:

2023-11-30T21:59:17-06:00   error       Failed to fetch configs of type 'calculated-metrics-log', skipping download of this type. Reason: Failed to get existing configs for API calculated-metrics-log (HTTP 400)!

    Response was: {"error":{"code":400,"message":"You are using the new log monitoring solution. Old API endpoints are disabled."}} (HTTP 400😞 {"error":{"code":400,"message":"You are using the new log monitoring solution. Old API endpoints are disabled."}}

Here the the API list from the logs. I don't see Management Zones listed:

2023-11-30T21:59:16-06:00   debug   Default soft memory limit set: 2.1 GB

2023-11-30T21:59:16-06:00   info    Loading manifest "manifest.yaml". Restrictions: groups=[], environments=["Prod"]

2023-11-30T21:59:17-06:00   debug   Concurrent Request Limit: 5, 'MONACO_CONCURRENT_REQUESTS' environment variable is NOT set, using default value

2023-11-30T21:59:17-06:00   info    API can not be downloaded and needs manual creation: 'kubernetes-credentials'.

2023-11-30T21:59:17-06:00   info    API can not be downloaded and needs manual creation: 'credential-vault'.

2023-11-30T21:59:17-06:00   info    API can not be downloaded and needs manual creation: 'extension'.

2023-11-30T21:59:17-06:00   info    API can not be downloaded and needs manual creation: 'azure-credentials'.

2023-11-30T21:59:17-06:00   info    API can not be downloaded and needs manual creation: 'aws-credentials'.

2023-11-30T21:59:17-06:00   info    Downloading from environment 'https://xxxxxxx.dynatrace-managed.com/e/xxxxxxxxxxxxxxxxxxxxxxxxxxxx' into project 'project_Prod'

2023-11-30T21:59:17-06:00   info    Downloading configuration APIs from 24 endpoints

2023-11-30T21:59:17-06:00   debug   APIs to download:

 - slo

 - calculated-metrics-application-mobile

 - custom-service-nodejs

 - calculated-metrics-application-web

 - synthetic-monitor

 - conditional-naming-processgroup

 - custom-service-php

 - service-resource-naming

 - conditional-naming-service

 - calculated-metrics-synthetic

 - reports

 - application-web

 - calculated-metrics-service

 - custom-service-go

 - synthetic-location

 - calculated-metrics-log

 - conditional-naming-host

 - dashboard

 - request-attributes

 - request-naming-service

 - custom-service-dotnet

 - application-mobile

 - custom-service-java

 - extension-elasticsearch

Thank you!

[AntonPineiro]

Hi,

Could you provide exact Monaco version with "monaco version"? And also, which command are you using to download configuration?

Best regards

[tfaqir-observe · Accepted solution]

Hi Anton, thanks for picking up my question so fast. I'm using monaco version 2.9.2. My command line is:
monaco download --manifest manifest.yaml --environment Prod

My manifest file looks like this:

manifestVersion: 1.0

projects:

- name: Prod

  path: Prod/

environmentGroups:

- name: managed

  environments:

  - name: Prod

    url:

        value: https://xxxxxxx.dynatrace-managed.com/e/xxxxxxxxxxxxxxxxxxxxxx

    auth:

      token:

        name: ENV_TOKEN_PRODUCTION_PROD

Over the weekend, after looking with rested eyes I was able to find the management zones tucked among the  "builtin" folders. I was looking for them in the non-builtin folders. Can you please shed some light on why the two different types of folders exist (folders names prepended with "builtin" and those without)? Do I need to make any special considerations when I deploy these downloaded configurations to our new SaaS environment/tenant?

Gratefully,

Tahir Faqir

[AntonPineiro]

Hi,

It is working as expected them.

My advice would be reading documentation and do not try to deploy everything in one shot. Going little by little, a good starting point is tags.

Best regards

[tfaqir-observe · Accepted solution]

Hi Anton, thanks for replying. I took your advice and read through the details and also watched Settings 2.0 Monaco 1 and Monaco 2 Observability Clinic videos. I now understand the new builtin schema names are the settings 2.0 compatible schemas. The names with simpler classic format are the older ones. Please feel free to add to or further clarify my answer.

Sincerely,

Tahir