[ 
https://issues.apache.org/jira/browse/FLINK-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092958#comment-16092958
 ] 

Chesnay Schepler commented on FLINK-7198:
-----------------------------------------

Here's the code taken from the {{JobManager.scala}}:

{code}
protected val jobManagerMetricGroup : Option[JobManagerMetricGroup] = 
metricsRegistry match {
    case Some(registry) =>
      val host = flinkConfiguration.getString(JobManagerOptions.ADDRESS)
      Option(new JobManagerMetricGroup(
        registry, NetUtils.unresolvedHostToNormalizedString(host)))
    case None =>
      log.warn("Could not instantiate JobManager metrics.")
      None
  }
{code}

So yes, currently we're just using {{jobmanager.rpc.address}}.

> Datadog Metric Reporter reports incorrect host for JobManager
> -------------------------------------------------------------
>
>                 Key: FLINK-7198
>                 URL: https://issues.apache.org/jira/browse/FLINK-7198
>             Project: Flink
>          Issue Type: Bug
>          Components: Metrics
>    Affects Versions: 1.3.1
>         Environment: RHEL 7.3, Mesos 1.3, Datadog
>            Reporter: Robert Batts
>            Priority: Minor
>
> When using the Datadog Metric Reporter with a Mesos deployed Flink 1.3.1 
> cluster the JobManager is reported to Datadog with a tag of host:127.0.0.1. 
> The TaskManagers report with the correct tag (i.e. host:mesos-02.place.com), 
> so this just appears to be an issue with the way host information is gathered 
> for Datadog.



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

Reply via email to