[
https://issues.apache.org/jira/browse/FLINK-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-8358:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Hostname used by DataDog metric reporter is not configurable
> ------------------------------------------------------------
>
> Key: FLINK-8358
> URL: https://issues.apache.org/jira/browse/FLINK-8358
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Metrics
> Affects Versions: 1.4.0
> Reporter: Elias Levy
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> The hostname used by the DataDog metric reporter to report metrics is not
> configurable. This can problematic if the hostname that Flink uses is
> different from the hostname used by the system's DataDog agent.
> For instance, in our environment we use Chef, and using the DataDog Chef
> Handler, certain metadata such a host roles is associated with the hostname
> in the DataDog service. The hostname used to submit this metadata is the
> name we have given the host. But as Flink picks up the default name given by
> EC2 to the instance, metrics submitted by Flink to DataDog using that
> hostname are not associated with the tags derived from Chef.
> In the Job Manager we can avoid this issue by explicitly setting the config
> {{jobmanager.rpc.address}} to the hostname we desire. I attempted to do the
> name on the Task Manager by setting the {{taskmanager.hostname}} config, but
> DataDog does not seem to pick up that value.
> Digging through the code it seem the DD metric reporter get the hostname from
> the {{TaskManagerMetricGroup}} host variable, which seems to be set from
> {{taskManagerLocation.getHostname}}. That in turn seems to be by calling
> {{this.inetAddress.getCanonicalHostName()}}, which merely perform a reverse
> lookup on the IP address, and then calling {{NetUtils.getHostnameFromFQDN}}
> on the result. The later is further problematic because it result is a
> non-fully qualified hostname.
> More generally, there seems to be a need to specify the hostname of a JM or
> TM node that be reused across Flink components.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
