Page Comparison

The pages in this topic are:

To monitor:

• PhixFlow tasks and actions, including which users have run them, use the System Console.
• configuration actions by users, use the System Console Audit Summary tab.
• user activity, for example when each user performed their last action, use the detailed user list.
• the activity of analysis modelling

• objects that move data, such as pipes, collectors and exporters, use the System Logging Configuration option Allow Logging to enable modelling object logging.

• With logging enabled you can then:  
  
  • either use the System Logging Configuration options in the Pipe Logging and Collector/Exporter Logging sections. These options switch on logging for all objects of a specific type.
  • or use the Log Traffic or equivalent

• • property to switch on logging for individual objects.
  Log messages are reported in the System Console with the activity that caused the modelling object to run. 

• Phixflow activity on the server and network, use the

• Server Log Files. These files are generated by:
  • the PhixFlow webapp
  • the Tomcat servlet.
• third-party operational system, e.g. Splunk, you can use a query to extract logging information from the PhixFlow database, see Logs for Third-Party Systems

PhixFlow generates processing statistics, which are saved to the database. These statistics are useful if you want to tune PhixFlow and its applications to improve performance; see Processing Statistics.