The metrics are not always the most clear on the UI, and trident does not make
it any clearer. First of all there are several different modes on the UI. You
can look at the metrics over different time periods, 10 mins, 3 hours, 1 day,
and all time. If you have clicked on one of these links the page will display
numbers for just this range, except in the section labeled for specific time
periods. There is also a button that decides if we should include system stats
or not. If this is selected the aggregate numbers will include acks. If it is
not selected they will not.
The other thing to be aware of is that trident is a layer that sits on top of
storm so the UI displays what the trident topology was compiled down to, not as
much of what your code looks like. Trident spouts actually run in a bolt, but
control logic is in the actual spout. You can still pull out the number of
messages that a trident spout emitted in most cases, but you need to know where
to look, and you might need to click on the component page for the bolt running
the spout to be able to divide the counts up by which stream they were written
to. - Bobby
On Monday, November 23, 2015 7:38 AM, Sachin Pasalkar
<[email protected]> wrote:
Hi,
We are developing the trident topology, we observed that the acking in UI
increase continuously even though we do not process any message. I found
description what those acks are
https://github.com/miguno/kafka-storm-starter/issues/5. However, is there any
plan to show users processed message? As a user, I am not interested in seeing
these acks. I am very much interesting in acks for my messages.
Thanks,
Sachin
