You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Robert Batts (JIRA)" <ji...@apache.org> on 2017/12/19 19:56:00 UTC

[jira] [Updated] (NIFI-4712) Allow Nifi to connect to Datadog through a proxy

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

Robert Batts updated NIFI-4712:
-------------------------------
    Labels: datadog metrics  (was: )

> Allow Nifi to connect to Datadog through a proxy
> ------------------------------------------------
>
>                 Key: NIFI-4712
>                 URL: https://issues.apache.org/jira/browse/NIFI-4712
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.4.0
>            Reporter: Robert Batts
>              Labels: datadog, metrics
>
> Nifi should be able to report metrics to Datadog via direct connection through a proxy. Currently, Nifi attempts a direct connection to Datadog (seen in the org.apache.nifi.reporting.datadog.DDMetricRegistryBuilder class) when a API key that is not "agent" is given. This connection should be allowed to go through a proxy instead of just being forced to use the agent. This should be as easy as a .withProxy() (https://github.com/coursera/metrics-datadog/blob/master/metrics-datadog/src/main/java/org/coursera/metrics/datadog/transport/HttpTransport.java#L83) and possibly adding a proxy host and proxy port attribute similar to what is used in the AWS modules.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)