[
https://issues.apache.org/jira/browse/FLINK-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-20055.
------------------------------------
Fix Version/s: 1.12.1
1.13.0
1.11.3
Resolution: Fixed
master: de527fdeec3887f6148ef3dfe7b2a024ec292522
1.12: 23fa6e9798b4d85af4189d8910500fb1ece34ac2
1.11: c430b9e67948ceadf078c37cdfa3285bbbfec886
> Datadog API Key exposed in Flink JobManager logs
> ------------------------------------------------
>
> Key: FLINK-20055
> URL: https://issues.apache.org/jira/browse/FLINK-20055
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration, Runtime / Metrics
> Affects Versions: 1.9.0
> Reporter: Florian Szabo
> Assignee: Florian Szabo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.3, 1.13.0, 1.12.1
>
>
> When Flink is set up to report metrics to Datadog, the JobManager log
> containe the Datadog API key in plain format. In fact it shows up in two
> different places:
> {code:java}
> 2020-08-03 09:03:19,400 INFO
> org.apache.flink.configuration.GlobalConfiguration - Loading
> configuration property: metrics.reporter.dghttp.apikey, <REDACTED-KEY>
> ...
> 2020-08-03 09:03:20,437 INFO org.apache.flink.runtime.metrics.ReporterSetup
> - Configuring dghttp with {apikey=<REDACTED-KEY>,
> tags=<...>,profile:<...>,region:<...>,env:<...>,
> class=org.apache.flink.metrics.datadog.DatadogHttpReporter}.
> {code}
> The expected behavior here should be that the API key in both places is
> hidden so that it does not end up in places where it should not be.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
