anchor.diff:  (See <<status_bar>> above for more information). Processors, Process Groups, and Remote Process Groups
   provide fine-grained details about their operations. Connections and Process Groups provide information 
   about the amount of data in their queues. The Summary Page provides information about all of the components
  -on the graph in a tabular format and also provides System Diagnostics information that includes disk usage,
  +on the canvas in a tabular format and also provides System Diagnostics information that includes disk usage,
   CPU utilization, and Java Heap and Garbage Collection information. In a clustered environment, this
   information is available per-node or as aggregates across the entire cluster. We will explore each of these 
   monitoring artifacts below.
  
positive.code: link:administration-guide.html[Admin Guide].
  
  In order to allow another NiFi instance to push data to your local instance, you can simply drag an <<input_port,Input Port>> onto the Root Process Group
  of your graph. After entering a name for the port, it will be added to your flow. You can now right-click on the Input Port and choose Configure in order
  to adjust the name and the number of concurrent tasks that are used for the port. If Site-to-Site is configured to run securely, you will also be given
  the ability to adjust who has access to the port. If secure, only those who have been granted access to communicate with the port will be able to see
  that the port exists.
  
negative.code: Other Management Features
  -------------------------
  
  In addition to the Summary Page, Data Provenance Page, Template Management Page, and Bulletin Board Page, there are other tools in the Management Toolbar (See <<User_Interface>>) that are useful to the DFM. The Flow Configuration History, which is available by clicking on the clock icon ( image:iconFlowHistory.png["Flow History", width=28] ) in the Management Toolbar, shows all the changes that have been made to the dataflow. The history can aid in troubleshooting, such as if a recent change to the dataflow has caused a problem and needs to be fixed. The DFM can see what changes have been made and adjust the flow as needed to fix the problem. While NiFi does not have an "undo" feature, the DFM can make new changes to the dataflow that will fix the problem.
  
  Two other tools in the Management Toolbar are the Controller Settings page ( image:iconSettings.png["Settings", width=28] ) and the Users page ( image:iconUsers.png["Users", width=28] ). The Controller Settings page provides the ability to change the name of the NiFi instance, add comments describing the NiFi instance, set the maximum number of threads that are available to the application, and create a back-up copy of the dataflow(s) currently on the canvas. It also provides tabs where DFMs may add and configure Controller Services and Reporting Tasks (see <<Controller_Services_and_Reporting_Tasks>>). The Users page is used to manage user access, which is described in the Admin Guide. 
  
  
  
  
  
  