Administration, Monitoring, and Maintenance
Day-to-day administration centers on the Admin area of the Gallery: managing users, roles, districts, collections, schedules, and credentials, plus viewing job results and logs. The AlteryxService logs, the Gallery logs, and MongoDB logs are the primary diagnostic sources; the System Settings and Admin panels surface service health. Monitoring includes watching queue depth, worker status, failed jobs, and disk usage of the persisted workflow directory and MongoDB.
Maintenance tasks: backups of MongoDB and the persisted workflow directory (both are required for a complete restore), purging old results to control disk growth, reviewing and disabling stale schedules, rotating API keys and credentials, applying patches, and monitoring license usage (seats and execution capacity). Data connections and credentials should be audited for orphaned entries when users leave.
Traps: backing up only MongoDB (you lose workflow files) or only the workflow directory (you lose metadata); assuming results are purged automatically (they accumulate and can fill disks); ignoring queue depth until jobs time out; and forgetting that a disabled user's schedules may still be active or may fail silently.
Worked example: The Gallery becomes slow and jobs queue. Check worker status first (are workers offline?), then queue depth, then disk space on the Controller and MongoDB. A full disk on the persisted workflow directory can stall publishing and execution-free space and purge old results.
Rule of thumb: a complete backup is MongoDB + persisted workflow directory together, taken consistently; either alone is an incomplete restore point.