[
https://issues.apache.org/jira/browse/FLINK-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773788#comment-16773788
]
Chesnay Schepler commented on FLINK-11692:
------------------------------------------
Assume we go with the proxy approach, what set of configurable options would
exist? Or to be more specific, would there be any option beyond host:port? (I'm
asking to ensure we don't lock ourselves into using OkHttpClient by exposing
library-specific options)
>From a quick search the URL approach might not work at all since it uses HTTPS
>and the client needs special logic to send this through a proxy.
> 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)
