[
https://issues.apache.org/jira/browse/FLINK-38946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Stoiev updated FLINK-38946:
--------------------------------
Description:
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:
# {*}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]
# *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 URL should be
updated from: {{[https://app.datadoghq.com/api/v1/series]}} to:
{{[https://api.datadoghq.com/api/v1/series]}}
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}}
was:
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.com}} is the official supported URL for API-based
integrations, whereas {{app.datadoghq.com}} is a legacy URL for this purpose.
Updating this endpoint provides two significant benefits:
# {*}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]
# *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.}} endpoint to route traffic
privately. Using {{app.}} 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 URL should be
updated from: {{[https://app.datadoghq.com/api/v1/series]}} to:
{{[https://api.datadoghq.com/api/v1/series]}}
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}}
> Update Datadog API endpoint from app.datadoghq to api.datadoghq
> ----------------------------------------------------------------
>
> 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
>
> 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:
> # {*}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]
> # *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 URL should be
> updated from: {{[https://app.datadoghq.com/api/v1/series]}} to:
> {{[https://api.datadoghq.com/api/v1/series]}}
> 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)
