Monitoring PhixFlow Tasks

The main method for monitoring PhixFlow tasks is via the System Console.

If you want to monitor PhixFlow from a third 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.
• 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

...

You can see when each user performed their last action by opening the detailed user list

You can see which tasks users have run in the System Console, including PhixFlow actions - i.e. when users have pressed a button on a PhixFlow form.

You can see what configuration actions users have performed by looking in the System Console Audit Summary tab.

Processing Statistics

PhixFlow generates processing statistics, which are saved to the database. These statics are for use by administrators and designers who are tuning for performance. See Processing Statistics for further detail.

System Logging

PhixFlow writes multiple log files into Tomcat's logs directory, where the level and content is determined by log4j.properties.

See Server Log Files for detailsstatistics are useful if you want to tune PhixFlow and its applications to improve performance; see Processing Statistics.