Metrics consumer vs new bolt

[Raphael Hsieh <ra...@gmail.com>]

What is the benefit of using a metrics consumer and generating metrics, as
opposed to just creating a new bolt to log metrics ?

How does it affect the speed of the topology?

from what I can tell, registering a metricsConsumer will effectively spawn
a new bolt. Only this bolt has access to metrics generated elsewhere in the
topology?

If I were to create a metric that purely counts the number of tuples in a
batch, how would that differ from creating a new bolt that aggregates the
number of tuples in a batch and then outputs it to a log file ?

Thanks
-- 
Raphael Hsieh

答复: Metrics consumer vs new bolt

[vlhf刘海峰 <hf...@Ctrip.com>]

Think about the convenience that storm builtin metric utils brought to you.

You don’t need to handle time bucket yourself, or even calculate average.

发件人: Raphael Hsieh [mailto:raffihsieh@gmail.com]
发送时间: 2014年9月30日 6:19
收件人: user@storm.apache.org
主题: Metrics consumer vs new bolt

What is the benefit of using a metrics consumer and generating metrics, as opposed to just creating a new bolt to log metrics ?

How does it affect the speed of the topology?

from what I can tell, registering a metricsConsumer will effectively spawn a new bolt. Only this bolt has access to metrics generated elsewhere in the topology?

If I were to create a metric that purely counts the number of tuples in a batch, how would that differ from creating a new bolt that aggregates the number of tuples in a batch and then outputs it to a log file ?

Thanks
--
Raphael Hsieh