Here's a concise feature request that frames the customer impact rather than just the implementation detail:

## Problem

Port's Datadog integration currently relies on an older version of the Datadog API. As customers begin investing more heavily in Datadog integrations, this is becoming a significant limitation—particularly for ingesting data from the Datadog Service Catalog, which depends on newer API capabilities.

## Customer Impact

* Blocks Service Catalog ingestion from Datadog.

* Prevents customers from leveraging newer Datadog platform capabilities.

* Forces workarounds or custom integrations for modern Datadog deployments.

* Makes it difficult to fully adopt Port as the engineering catalog when Datadog is a primary source of truth.

## Requested Enhancement

Upgrade the Datadog integration to use the current Datadog API (v2.2+), enabling support for Service Catalog ingestion and other modern API capabilities.

## Customer Context

A customer recently began implementing the Datadog integration and immediately encountered this limitation. Their observability engineering team is now involved, and this is expected to become a key discussion point as they expand their Datadog usage.

## Success Criteria

* Datadog integration supports the latest stable Datadog APIs.

* Service Catalog entities can be ingested into Port.

* Future Datadog capabilities can be adopted without requiring a major integration rewrite.

This version is likely to get more traction internally because it focuses on , not just "please upgrade the API." It also avoids locking the engineering team into a specific API version while still making the need clear.