anchor.diff:  
   One of the most powerful features of NiFi is the ability to route FlowFiles based on their Attributes. The primary mechanism
   for doing this is the RouteOnAttribute Processor. This Processor, like UpdateAttribute, is configured by adding user-defined properties.
  -Any number of properties can be added by clicking the "New Property" icon in the top-right corner of the Properties tab in the
  +Any number of properties can be added by clicking the "+" button in the top-right corner of the Properties tab in the
   Processor's Configure dialog.
   
   Each FlowFile's Attributes will be compared against the configured properties to determine whether or not the FlowFile meets the
  
positive.code: image:provenance-table.png[Provenance Table]
  
  Initially, this table is populated with the most recent 1,000 Provenance Events that have occurred (though it may take a few
  seconds for the information to be processed after the events occur). From this dialog, there is a Search button that allows the
  user to search for events that happened by a particular Processor, for a particular FlowFile by filename or UUID, or several other
  fields. The `nifi.properties` file provides the ability to configure which of these properties are indexed, or made searchable.
  Additionally, the properties file also allows you to choose specific FlowFile Attributes that will be indexed. As a result, you can
  
negative.code: The connections between Processors also expose the number of items that are currently queued.
  
  It may also be valuable to see historical values for these metrics and, if clustered, how the different nodes compare to one another.
  In order to see this information, we can right-click on a component and choose the `Stats` menu item. This will show us a graph that spans
  the time since NiFi was started, or up to 24 hours, whichever is less. The amount of time that is shown here can be extended or reduced
  by changing the configuration in the properties file.
  
  