[
https://issues.apache.org/jira/browse/NIFI-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287893#comment-16287893
]
Joseph Witt commented on NIFI-3293:
-----------------------------------
[~pvillard] [~mattyb149] I'm not sure we should go down this route as-is.
Counters are not part of the nifi-api and this change makes them so. They
are/were intended to be an internal scratch space for developers to observe
ad-hoc specific items of interest that can be counted over undefined sets of
time/etc.. This patch makes it easy to grab them and send them externally but
effectively bypasses any authorization/sensitive concerns. Presently getting
access to counter data is available via REST API calls and subject to the
authentication and authorization model.
In short, i think this is exposing counters beyond what they were intended for
without addressing the full scope of sensitivity.
> Expose counter repository to reporting tasks
> --------------------------------------------
>
> Key: NIFI-3293
> URL: https://issues.apache.org/jira/browse/NIFI-3293
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Minor
>
> At the moment a {{ReportingTask}} cannot access {{CounterRepository}}. It
> would be nice to add this feature allowing reporting tasks to send counters
> data.
> A first implementation would be to add counters data in metrics sent by the
> Ambari Reporting Task so that custom graphs can be easily added in tools such
> as Grafana.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
