[
https://issues.apache.org/jira/browse/NIFI-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030020#comment-16030020
]
ASF GitHub Bot commented on NIFI-106:
-------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/1872
@mcgilman great point! When I looked through the code, I saw the section of
code that was handling permissions around the Status History but didn't look
close enough. I had assumed that if the user doesn't have read permissions on
the processor, that the stats would be made unavailable. However, looking
again, I see that what we do is allow access to the stats but just blank out
the name of the Processor.
What probably makes sense, then, is to filter out any stats that come from
counters unless the user does have read permissions to the Processor. I.e., if
User A has no read permissions to a processor, its stats would return just the
way they are now, with just the pre-defined Bytes In, Bytes Out, FlowFiles In,
FlowFiles out, etc. But if the user does have read permissions, then they will
also see all stats for counters emitted by that processor (but not
type-specific counters, just instance-specific counters). Thoughts?
> Processor Counters should be included in the Status Reports
> -----------------------------------------------------------
>
> Key: NIFI-106
> URL: https://issues.apache.org/jira/browse/NIFI-106
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 1.3.0
>
>
> This would allow a Processor's Status HIstory to show counters that were
> maintained over time periods instead of having only a single count since
> system start.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
