markap14 commented on code in PR #6156:
URL: https://github.com/apache/nifi/pull/6156#discussion_r908955784


##########
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/nifi.properties:
##########
@@ -345,6 +345,14 @@ nifi.diagnostics.on.shutdown.max.filecount=10
 # The diagnostics folder's maximum permitted size in bytes. If the limit is 
exceeded, the oldest files are deleted.
 nifi.diagnostics.on.shutdown.max.directory.size=10 MB
 
+# Performance tracking properties
+## Specifies what percentage of the time we should track the amount of time 
processors are using CPU, reading from/writing to content repo, etc.
+## This can be useful to understand which components are the most expensive 
and to understand where system bottlenecks may be occurring.
+## The value must be in the range of 0 (inclusive) to 100 (inclusive). A 
larger value will produce more accurate results, while a smaller value may be
+## less expensive to compute.
+## Results can be obtained by running "nifi.sh diagnostics <filename>" and 
then inspecting the produced file.
+nifi.performance.tracking.percentage=${nifi.performance.tracking.percentage}

Review Comment:
   Fair enough, I can update the admin guide. I don't want to mention 
`diagnostics` in the property name. These are not really related to diagnostics 
necessarily. That just happens to be the only mechanism by which we can expose 
them currently. But in the future, I can imagine them being exposed via 
Reporting Tasks and/or the UI, etc.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to