Dynatrace Gen3 tenants no longer expose the classic slo.read / “Read SLO” scope for classic API tokens. Because of this, customers with newer Dynatrace tenants cannot ingest SLOs into Port using the current self-hosted Ocean Dynatrace integration.

The current integration expects a classic Dynatrace API token and uses the classic SLO API. For Gen3 tenants, SLO access requires OAuth client credentials and the newer SLO API with scopes such as slo:slos:read.

Request: update the Dynatrace Ocean integration and documentation to support Gen3 SLO ingestion via OAuth client credentials, while preserving the existing classic API-token flow for older tenants.

Customer impact: World Bank cannot ingest Dynatrace SLOs into Port from their Gen3 Dynatrace tenant. Other Dynatrace resources may work, but SLO ingestion is blocked.