You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/01/31 11:45:00 UTC
[jira] [Commented] (NIFI-2724) JMX Processor
[ https://issues.apache.org/jira/browse/NIFI-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346658#comment-16346658 ]
ASF GitHub Bot commented on NIFI-2724:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/1016
@brianburnett You didn't respond to the feedback from @pvillard31. Do you need help getting this pushed through?
> 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 F de Miranda
> 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
(v7.6.3#76005)