GitHub user HeartSaVioR opened a pull request:

    https://github.com/apache/storm/pull/1325

    STORM-1700 Introduce 'whitelist' / 'blacklist' option to MetricsConsumer 
(1.x)

    > NOTE: This is based on STORM-1698, PR #1323  
    
    * Users can set whitelist or blacklist to filter out metrics by name
      * if none of them specified (by default), no metrics are filtered out
    * how to match: substring match with regular expression
      * use both ^ and $ when you want to match strictly (full string match)
    * added unit test

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/HeartSaVioR/storm STORM-1700-1.x

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1325.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1325
    
----
commit 2dce735bacc5eb1ff7de5ca9f161373767e4f30d
Author: Jungtaek Lim <[email protected]>
Date:   2016-04-08T04:05:00Z

    STORM-1698 Asynchronous MetricsConsumerBolt
    
    * change MetricsConsumerBolt's behavior to asynchronus manner
      * to avoid bad side effect of topology
    * for details please refer JIRA issue: 
https://issues.apache.org/jira/browse/STORM-1698

commit ff96564282f8d3085876d885e2f3714125fff53a
Author: Jungtaek Lim <[email protected]>
Date:   2016-04-09T05:11:20Z

    STORM-1700 Introduce 'whitelist' / 'blacklist' option to MetricsConsumer
    
    * Users can set whitelist or blacklist to filter out metrics by name
      * if none of them specified (by default), no metrics are filtered out
    * how to match: substring match with regular expression
      * use both ^ and $ when you want to match strictly (full string match)
    * added unit test

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to