Xin Liu created STORM-2780:
------------------------------
Summary: MetricsConsumer record unnecessary timestamp
Key: STORM-2780
URL: https://issues.apache.org/jira/browse/STORM-2780
Project: Apache Storm
Issue Type: Improvement
Components: storm-client
Reporter: Xin Liu
Assignee: Xin Liu
In a topology I could call
conf.registerMetricsConsumer(LoggingMetricsConsumer.class,2);
to generate a file named worker.log.metrics with metrics data.
like this:
2017-10-17 10:16:13,272 307174 1508206573 host1:6702 16:count
__fail-count {}
2017-10-17 10:16:13,272 307174 1508206573 host1:6702 16:count
__emit-count {default=41700}
2017-10-17 10:16:13,272 307174 1508206573 host1:6702 16:count
__execute-count {split:default=41700}
2017-10-17 10:29:20,898 126900 1508207360 host1:6702 29:spout
__ack-count {}
2017-10-17 10:29:20,906 126908 1508207360 host1:6702 29:spout
__sendqueue {sojourn_time_ms=0.0, write_pos=299526,
read_pos=299526, overflow=1, arrival_rate_secs=2643.9024390243903,
capacity=1024, population=0}
But it records both date-and-timestamp(2017-10-17 10:29:20,906 126908) and
only-timestamp(1508207360),I think the only-timestamp should be deleted because
it's unnecessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)