tree 9494261d2f35be34e97993804204c2a4e5e82554
parent 0fd0e1ba25c22779c3533dd7873c4fce856b4da6
author Rajan Dhabalia <rdhabalia@apache.org> 1557914737 -0700
committer Jia Zhai <zhaijia@apache.org> 1557914737 +0800

[pulsar-storm] add more metrics to troubleshoot spout throughput (#4280)

### Motivation

Many time user sees lower throughput in pulsar-spout even though standalone consumer can consume such msgRate easily. It would be hard to debug user's topology without enough information so, adding two metrics which can impact spout throughput.
- number of message filed: spout sleeps when it sees failed message so, it's important to have visibility of that count
- number of times spout-thread not found the message in queue: spout topology internally sleeps if it doesn't see any emitted tuple in collector after triggering `nextTuple()` api.

This metrics gives more visibility about consumer throughput.