Support new settings 2.0 API schema

[didiladi]

Describe the solution you'd like monaco needs to support the new settings 2.0 API schema, which will be used in all APIs added to Dynatrace in the future. This means that by supporting the spec, monaco will be able to support all future APIs in Dynatrace without any hassle.

[ghost]

I'm trying to add the settings/objects endpoint and coming up on issues. I think I need a way to drill further into the GET all so in effect it's items.value

My api.go is:

// Early adopter API !
"settings-objects": {
  apiPath: "/api/v2/settings/objects",
  propertyNameOfGetAllResponse: "items",
},

The JSON response for GET all is:

{
  "items": [{
      "objectId": "**************",
      "value": {
        "enabled": true,
        "name": "entity:myEntity",
        "displayName": "myEntity",
        "createdBy": "Adam Gardner",
        "rules": [{
            "idPattern": "{id}",
            "instanceNamePattern": "{id}",
            "sources": [{
                "sourceType": "Metrics",
                "condition": "$eq(devices.discovered)"
              }],
            "attributes": [{
                "key": "site",
                "displayName": "site",
                "pattern": "{site}"
              },
              {
                "key": "name",
                "displayName": "name",
                "pattern": "{name}"
              }]
          }]
      }
    }],
  "totalCount": 1,
  "pageSize": 100
}

[AH-ErikPost]

Is there any update on supporting the settings 2.0 API schemes?

[heckelmann]

Describe the solution you'd like monaco needs to support the new settings 2.0 API schema, which will be used in all APIs added to Dynatrace in the future. This means that by supporting the spec, monaco will be able to support all future APIs in Dynatrace without any hassle.

+1

[dischello]

+1

[Simon-Boyer]

Hello. I was wondering if any work is being done on this. One of our client needs to use Monaco to configure anomaly-detection at the host level, which should be possible if the v2 settings api was supported.

I've also made a small PoC for the setting object we needed. You probably cannot use it as is since it is not really a generic solution but maybe it can give ideas: https://github.com/Simon-Boyer/dynatrace-monitoring-as-code/tree/experiment/v2-settings-object

[UnseenWizzard]

Hi @Simon-Boyer this is indeed being worked on and we plan to release monaco 2.0 with general support for Settings configuration soon

[UnseenWizzard]

Settings 2.0 are suppored by monaco 2.0 which is available as pre-release