Settings v1 → Settings 2.0

Settings v1 → Settings 2.0

Gen2 used the Configuration API v1 with JSON payloads per config type. Gen3 uses Settings 2.0 — a unified, schema-based API where every setting follows the same pattern.

Key Differences

GEN2 Settings v1                        GEN3 Settings 2.0
──────────────────────────────────────  ──────────────────────────────────────
Separate API per config type            Unified /settings/objects endpoint
Custom JSON per type                    Schema-based (schemaId + value)
No schema validation                    Server-side schema validation
Limited scoping                         Scope: environment, host, service, etc.
No versioning                           Object versioning built-in

Settings 2.0 Pattern

// POST /api/v2/settings/objects (or /platform/classic/environment-api/v2/settings/objects)
[{
  "schemaId": "builtin:anomaly-detection.metric-events",
  "scope": "environment",
  "value": {
    "enabled": true,
    "summary": "My Alert",
    "queryDefinition": { ... },
    "modelProperties": { ... },
    "eventTemplate": { ... }
  }
}]

Common Schema IDs

Schema ID                                   Replaces (Gen2)
──────────────────────────────────────────  ──────────────────────────
builtin:davis.anomaly-detectors             Metric events (Gen3 native)
builtin:anomaly-detection.metric-events     Metric events (classic)
builtin:tags.auto-tagging                   Auto-tagging rules
builtin:process-group.monitoring.state      Process group monitoring
builtin:rum.web.injection                   RUM injection settings
builtin:logmonitoring.log-storage-settings  Log storage rules
builtin:ownership.teams                     Team ownership (NEW in Gen3)

Discovering Schemas

# List all available schemas
GET /api/v2/settings/schemas

# Get schema details
GET /api/v2/settings/schemas/builtin:davis.anomaly-detectors

# List objects for a schema
GET /api/v2/settings/objects?schemaIds=builtin:davis.anomaly-detectors

Terraform Integration

The Dynatrace Terraform provider maps Settings 2.0 schemas to resources:

resource "dynatrace_davis_anomaly_detectors" "cpu_alert" {
  title   = "[P1] High CPU"
  enabled = true
  # ... analyzer config
}

Use terraform import to bring existing settings into state, or Monaco download to export all settings as code.