[
https://issues.apache.org/jira/browse/FLINK-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773109#comment-16773109
]
Chesnay Schepler commented on FLINK-11692:
------------------------------------------
I believe other http reporters don't require this as they have a configurable
host.
>From what I understand this should be straight-forward; add a configurable
>host that is inserted into the URLs (see DatadogHttpClient#SERIES_URL_FORMAT
>and DatadogHttpClient#VALIDATE_URL_FORMAT); and by default we use
>{{app.datadoghq.com}}.
I've given you contributor permission in case you want to start working on this.
> Add Proxy for DataDog Metric Reporter
> -------------------------------------
>
> Key: FLINK-11692
> URL: https://issues.apache.org/jira/browse/FLINK-11692
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
> Reporter: Scott Mitchell
> Priority: Minor
>
> There's no clear way currently to route just metric traffic through a proxy.
> Although one can use java http proxy environment variables and an extensive
> blacklist, the solution is far from elegant or robust. It would be great to
> have a proxy option for the DataDog metric reporter, and other http metric
> reporters if the solution is easily extendable.
>
> Additional sample config lines:
> {code:java}
> metrics.reporter.dghttp.proxyHost: my.proxy.com
> metrics.reporter.dghttp.proxyPort: 8080{code}
>
> I can take this ticket myself, unless there is already another robust
> solution to route just metric data through a proxy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
