You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Eui Heo (Jira)" <ji...@apache.org> on 2019/12/05 23:55:00 UTC

[jira] [Commented] (FLINK-14812) Add metric libs to Flink classpath with an environment variable.

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

Eui Heo commented on FLINK-14812:
---------------------------------

I also think it's better to give it a name that can be used for more general purposes.

> Add metric libs to Flink classpath with an environment variable.
> ----------------------------------------------------------------
>
>                 Key: FLINK-14812
>                 URL: https://issues.apache.org/jira/browse/FLINK-14812
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes, Deployment / Scripts
>            Reporter: Eui Heo
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> To use the Flink metric lib you need to add it to the flink classpath. The documentation explains to put the jar file in the lib path.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/metrics.html#prometheus-orgapacheflinkmetricsprometheusprometheusreporter
> However, to deploy metric-enabled Flinks on a kubernetes cluster, we have the burden of creating and managing another container image. It would be more efficient to add the classpath using environment variables inside the constructFlinkClassPath function in the config.sh file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)