[ https://issues.apache.org/jira/browse/NIFI-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870785#comment-15870785 ]
ASF GitHub Bot commented on NIFI-2724: -------------------------------------- Github user brianburnett commented on the issue: https://github.com/apache/nifi/pull/1016 $git log commit df73bdc7f0f13d4f21b23a8a0a41f78fa0386aa2 Author: brianburnett <brian.burn...@capitalone.com> Date: Thu Feb 16 11:55:55 2017 -0500 NIFI-2724 JMX Processor 1.2.0 rev $git cherry-pick df73bdc7f0f13d4f21b23a8a0a41f78fa0386aa2 On branch nifi-2724v2 You are currently cherry-picking commit df73bdc. nothing to commit, working tree clean The previous cherry-pick is now empty, possibly due to conflict resolution. If you wish to commit it anyway, use: git commit --allow-empty Otherwise, please use 'git reset' Shall I do the git commit --allow-empty? > 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 > Assignee: Andre > Priority: Minor > Labels: processor > 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.15#6346)