nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-2724) JMX Processor
Date Tue, 13 Sep 2016 19:21:20 GMT

    [ https://issues.apache.org/jira/browse/NIFI-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488147#comment-15488147
] 

ASF GitHub Bot commented on NIFI-2724:
--------------------------------------

GitHub user brianburnett opened a pull request:

    https://github.com/apache/nifi/pull/1016

    NIFI-2724 New JMX Processor

    Attempt to contribute GetJMX Processor

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

    $ git pull https://github.com/brianburnett/nifi nifi-2724

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

    https://github.com/apache/nifi/pull/1016.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 #1016
    
----
commit acdb3252ad330b829386e1b378eb013072cd4c15
Author: brianburnett <brian.burnett@capitalone.com>
Date:   2016-09-13T19:13:00Z

    NIFI-2724 New JMX Processor

----


> JMX Processor
> -------------
>
>                 Key: NIFI-2724
>                 URL: https://issues.apache.org/jira/browse/NIFI-2724
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: 1.0.0
>         Environment: All platforms with Java RMI support for JMX
>            Reporter: Brian Burnett
>            Priority: Minor
>              Labels: processor
>             Fix For: 1.1.0
>
>         Attachments: 0001-NIFI-2724-New-JMX-Processor.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The JMX Processor feature addition includes only GetJMX without SecurityManager capabilities
at this time.  The processor in its current state is capable of pulling MBean Property and
Attribute values from a remote RMI Server.  Each set of Mbean data is wrapped in a JSON formatted
FlowFile for downstream processing.  It has the ability to control content with whitelist
and blacklist properties.
> Possible use for this processor and the reason it was created is to help make sense of
Kafka server metrics.
> Will followup with a SecurityManager Context Service and PutJMX Processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message