[
https://issues.apache.org/jira/browse/FLINK-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009658#comment-16009658
]
ASF GitHub Bot commented on FLINK-6221:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3833
Yu can find an example on how to shade here:
https://github.com/apache/flink/blob/master/flink-metrics/flink-metrics-datadog/pom.xml.
Shading dependencies in reporters/connectors has become a safety-precaution
form our side.
It is not that unlikely that user-code contains the same dependencies. For
one user-code also includes other reporters, so by the very existence of this
reporter there is a precedent :) Besides that something that pops up from time
to time on the mailing lists is users talking to REST endpoints in their
functions/source/sinks, which may also rely on http-related dependencies.
> Add Prometheus support to metrics
> ---------------------------------
>
> Key: FLINK-6221
> URL: https://issues.apache.org/jira/browse/FLINK-6221
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
> Affects Versions: 1.2.0
> Reporter: Joshua Griffith
> Assignee: Maximilian Bode
> Priority: Minor
>
> [Prometheus|https://prometheus.io/] is becoming popular for metrics and
> alerting. It's possible to use
> [statsd-exporter|https://github.com/prometheus/statsd_exporter] to load Flink
> metrics into Prometheus but it would be far easier if Flink supported
> Promethus as a metrics reporter. A [dropwizard
> client|https://github.com/prometheus/client_java/tree/master/simpleclient_dropwizard]
> exists that could be integrated into the existing metrics system.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
