- This line was added.
- This line was removed.
- Formatting was changed.
As an XNAT Administrator, there are times when it is helpful to know what processes are running, who is running them, and if they have been running far longer than expected. This can both affect and be affected by overall system performance. It is also a good idea to ensure that any planned service interruptions are as minimally disruptive to your users' work as possible.
There are a few ways to monitor and track pipeline processing in XNAT.
Monitoring Pipeline and User Workflows in the Admin UI
Go to Administer > More > View All Workflows in the top navigation. This will display a very large data table consisting of every user workflow entry that XNAT has logged.
This data table is powered by a stored search that is automatically generated by XNAT. You can right-click on the pipeline_name column to set a filter for specific pipelines, and/or click on the Userfullname column to set a filter on a specific user. You can also save these modified data tables out as separate stored searches for future reference.
Any pipeline that is still running will have a status of "Running".
Monitoring All User Activity in the Admin UI
Go to Administer > More > Summary in the top navigation. This will display a modal with a series of usage reports in it. You can toggle the timeframe of these reports with the selectors at the top of the modal window.
In this summary window, there is a summary of user workflows titled "Pipelines" that has a count of successful and failed runs.
Debugging Stalled or Failed Pipelines
From your command line, SSH into your XNAT and go to PIPELINE_HOME/logs. This directory contains timestamped log files which can be used to troubleshoot pipeline runs.
By default, PIPELINE_HOME is set to
If a pipeline is launched from XNAT and continues to be in Queued/Running state, the file TOMCATXNAT_HOME/webapps/XNAT_PROJECT/logs/applicationlaunch.log contains the exact command statement which failed to launch. Copy and run this statement from a command prompt as a tomcat user to figure out cause of failure.
The log file XNAT_HOME/logs/pipeline.log logs any failed pipeline runs, and can be a useful place to debug.
By default, TOMCATXNAT_HOME is set to