Julio Biason created FLINK-8284:
-----------------------------------
Summary: Custom metrics not being exposed for Prometheus
Key: FLINK-8284
URL: https://issues.apache.org/jira/browse/FLINK-8284
Project: Flink
Issue Type: Bug
Components: Documentation, Metrics
Affects Versions: 1.4.0
Environment: Linux/CentOS 7
Reporter: Julio Biason
Following the documentation, we changed our filter that removes events with
missing fields to a RichFilterFunction, so we can capture metrics about such
events:
{{public class MissingClientFilter extends RichFilterFunction<LineData> {
private transient Counter counter;
@Override
public void open(Configuration config) {
this.counter = getRuntimeContext()
.getMetricGroup()
.addGroup("events")
.counter("missingClient");
}
@Override
public boolean filter(LineData line) {
String client = line.get("client").toString();
boolean missing = client.trim().equals("");
if (!missing) {
this.count();
}
return !missing;
}
private void count() {
if (this.counter != null) {
this.counter.inc();
}
}
}}}
We also added Prometheus as our reporter:
{{metrics.reporters: prom
metrics.reporter.prom.port: 9105
metrics.reporter.prom.class:
org.apache.flink.metrics.prometheus.PrometheusReporter}}
The problem is accessing port 9105 display all Flink metrics, but not ours.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
