Github user zd-project commented on the issue:
https://github.com/apache/storm/pull/2714
Some questions:
1. Currently, by rejecting a metric, StormMetricsRegistry simply discard it
and log the warning without throwing any errors to the calling method/classes.
Is this an appropriate practice?
2. Should we instead use a secondary registry for filtering and reporting
only, apart from the primary which does include all registrations?
3. Not sure how to handle RocksDB metrics as it isn't technically a daemon.
---
