You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ivan Stoiev (Jira)" <ji...@apache.org> on 2026/01/20 09:31:00 UTC

[jira] [Updated] (FLINK-38946) Allow AWS PrivateLink/GCP Cloud Private Service Connect for Datadog integration

     [ https://issues.apache.org/jira/browse/FLINK-38946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Stoiev updated FLINK-38946:
--------------------------------
    Summary: Allow AWS PrivateLink/GCP Cloud Private Service Connect for Datadog integration  (was: Allow AWS VPC Endpoint/GCP Cloud Private Service Connect for Datadog integration)

> Allow AWS PrivateLink/GCP Cloud Private Service Connect for Datadog integration
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-38946
>                 URL: https://issues.apache.org/jira/browse/FLINK-38946
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>            Reporter: Ivan Stoiev
>            Priority: Minor
>              Labels: pull-request-available
>
> The current implementation of the {{DatadogHttpClient}} in the {{flink-metrics-datadog}} module uses {{app.datadoghq.com}} (or regional variants) as the base URL for sending metrics.
> Using {{api.datadoghq}} is the official supported URL prefix for API-based integrations, whereas {{app.datadoghq}} is a legacy URL for this purpose. Updating this endpoint provides two significant benefits:
> 1. {*}Official Support{*}: It aligns the Flink integration with Datadog's supported API host standards. This is particularly relevant for the following calls:
> * *Submit Metrics:* [{{/api/v1/series}}|https://docs.datadoghq.com/api/latest/metrics/#submit-metrics]
> * *Validate API Key:* [{{/api/v1/validate}}|https://docs.datadoghq.com/api/latest/authentication/#validate-api-key]
> 2. *Private Networking Support:* Many modern cloud networking features, such as *AWS VPC endpoints (PrivateLink)* and {*}GCP Cloud Private Service Connect{*}, specifically require the use of the {{api.datadoghq}} endpoint to route traffic privately. Using {{app.datadoghq}} prevents these integrations from working in restricted network environments.
> * [AWS PrivateLink Documentation|https://docs.datadoghq.com/agent/guide/private-link/?tab=crossregionprivatelinkendpoints]
> * [GCP Private Service Connect Documentation|https://docs.datadoghq.com/agent/guide/gcp-private-service-connect/?site=eu]
> *Proposed Change:* In {{{}DatadogHttpClient.java{}}}, the base URLs should be updated from: {{[https://app.datadoghq.%s/...]}} to: {{[https://app.datadoghq.%s/...]}}
> This change ensures that metric submissions follow the recommended path for programmatic access and enables compatibility with private connectivity solutions.
> *Affected File:* {{flink-metrics/flink-metrics-datadog/src/main/java/org/apache/flink/metrics/datadog/DatadogHttpClient.java}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)