Dynatrace API changelog version 1.266

Environment API

• User sessions API
  • New possible value in the reasonForNoSessionReplay field of the UserSession object:
    KILLED_INVALID_RESPONSE

• Extensions 2.0 API
  • New field in the ExtensionAssetsDto object:
    errors (string)

• Networks zones API
  • New fields in the NetworkZone object:
    overridesGlobal (boolean)
    scope (string)

• Settings API
  • New field in the SettingsObject object:
    modificationInfo (ModificationInfo)

Configuration API

• Service metrics API
  • Modified limit of the values field in the ComparisonInfo object:
    10 –> 50
• Request naming API
  • Modified limit of the values field in the ComparisonInfo object:
    10 –> 50

• Extensions API
  • New possible value in the technology query parameter:
    DYNATRACE
• Request attributes API
  • New possible value in the serviceTechnology field of the ScopeConditions object:
    DYNATRACE

Cluster API

• /networkZones
  • New fields in the NetworkZone object:
    overridesGlobal (boolean)
    scope (string)

• /settings/objects
  • New field in the SettingsObject object:
    modificationInfo (ModificationInfo)

• /synthetic/locations
  • New field in the PrivateSyntheticLocation object:
    useNewKubernetesVersion (boolean)

GA availability

The following API is now available in GA:

• Environment API POST /securityProblems/mute
• Environment API POST /securityProblems/unmute
• Environment API POST /securityProblems/{id}/remediationItems/mute
• Environment API POST /securityProblems/{id}/remediationItems/unmute

Deprecation

The following API is now deprecated:

• Configuration API Anomaly detection API - Metric events—use the Settings API with the Metric events (builtin:anomaly-detection.metric-events) schema instead. To learn how to migrate from Metric events API to Settings API, see the migration guide.