[
https://issues.apache.org/jira/browse/FLINK-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999521#comment-15999521
]
ASF GitHub Bot commented on FLINK-6221:
---------------------------------------
Github user mbode commented on the issue:
https://github.com/apache/flink/pull/3833
Thanks for looking at it so quickly! I somewhat had the same instinct as
far as your first point is concerned and thought about pulling out a
`DropwizardReporter` without Scheduling but decided against it to not have to
touch too many places. I like your suggestion of converting metrics directly
without using Dropwizard as an intermediate step and am going to try that.
> Add Promethus 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)
