[
https://issues.apache.org/jira/browse/FLINK-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007215#comment-16007215
]
ASF GitHub Bot commented on FLINK-6221:
---------------------------------------
Github user hadronzoo commented on the issue:
https://github.com/apache/flink/pull/3833
@mbode thanks for working on this!
One thing that I've found useful when exporting Flink's statsd metrics to
Prometheus is to make several of the metric fields tags: like `job_name`,
`task_name`, `operator_name`, etc. This [statsd-exporter
mapping](https://gist.github.com/hadronzoo/621b6a6dce7e2596d5643ce8d1e954ea)
has tags that have worked well for me. I'm not tagging host names or IP
addresses because Prometheus's Kubernetes support does that already, but that
could be useful for people running standalone clusters.
> 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)
