Logs - Automate_Studio_Manager - Latest

Automate Studio Manager User Guide
Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio Manager
Version
Latest
ft:locale
en-US
Product name
Automate Studio Manager
ft:title
Automate Studio Manager User Guide
Copyright
2025
First publish date
2018
ft:lastEdition
2026-04-19
ft:lastPublication
2026-04-19T05:25:12.001000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Automate
L4_Investment_Segment
SAP Automation
L5_Product_Group
Winshuttle Enterprise
L6_Product_Name
Automate Studio
Automate Studio Manager
Table 1. Changes in this topic
Change type Description
Introduced in version 25.2 Global administrators can now fetch and download logs from multiple servers directly from the Studio Manager website. Logs can be fetched for a specific time window and downloaded as a compressed ZIP file, making it easy to access and manage recent server activity.
As a Global Administrator, you can do the following on the Logs page:
  • Enable logging
  • Set logging options, such as frequency and the type of messages logged (only Global Administrators can set log levels)
  • For Destination Path for Log Files, you have the option to provide a network path
  • Fetch and download server logs.

Edit Logs Settings

To edit logs settings, perform the following:
  1. Go to Settings > Logs.
  2. Click Edit to update the logs.
  3. From the Enable Logging drop-down list, select from the following log types: 
    Log Type Details

    Error

    Error logs highlight when the flow of execution is stopped due to a failure in the current activity only - and not due to an application-wide failure.

    Error messages should contain the entire Exception and not just the stack trace or message. This level of logging affects performance the least.

    Warning

    Warning logs highlight an abnormal or unexpected event in the application flow, but do not cause the application execution to stop.

    These should log exceptions; they should not stop the call flow but only be logged into the file system. Errors are also included in this level.

    Information

    These logs track the general flow of the application, and should be used to trace messages throughout the application flow.

    Because string composition is not done at this level, variable data is not written at this level. Errors and Warnings are included in this level.

    All

    This is the most detailed logging level. It includes variable data, so string composition is done extensively which can trigger more frequent collections, etc.

    Errors, Warnings, and Informational Messages are also included in this level. This level of logging has the highest impact on performance.
  4. Define the maximum log file size in MB in the File Size field. Logs larger than the size specified roll over to the next log file.
  5. Specify a value in the Maximum Rolling File Count. The specified value will be the maximum number of log files to use in the log file rotation on a given day. The default value is 10 files, but you can designate any number of files. For example, if you have a maximum log file size of 10 MB and you specify a Maximum Rolling File Count value of 10 files, the process will create 10 files of 10 MB each. At that point, if additional logs are created, the first file that was created will be deleted and a new file with the incoming logs will be created - and this process will happen on a rolling basis, ensuring that on any given day the logs do not unnecessarily fill the available space.
  6. Specify the destination path in the Destination Path for Log Files.
    Tip: If you provide a network path for Destination Path for Log Files, all server and worker logs will be written in the same folder. App Pool users should have read and write permissions to that folder. If you provide only a folder name and not an absolute path, the folder will be created at the install location of each server and the logs will be saved in that folder.
  7. Click Save.

Downloading logs from the Studio Manager website

Starting with Automate v25.2, global administrators can fetch and download application server logs directly from the Studio Manager website. This feature streamlines troubleshooting by allowing quick access to recent server logs without requiring direct server access.

To download the logs, perform the following steps:
  1. Go to Settings > Logs.
  2. Click Fetch Logs to initiates the process to collect logs from all Studio Manager application servers.
    • A Set Duration dialog box will appear prompting you to enter the time window (in minutes) for which you want to collect logs.
    • The maximum allowed value is 60 minutes.
    • Enter the desired number of minutes and confirm.
    Tip: Studio Manager schedules background jobs on all application servers to collect logs updated or created within the specified time window. While jobs are running, both the Fetch Logs and Download buttons are disabled. You can use the Refresh button to check if the logs files are available for download.
  3. Once all jobs are complete, click Download to receive a ZIP file containing the logs from all relevant servers.
    Note:
    • You can download only Studio Manager application server logs. Worker server logs are not available for download.
    • If multiple Studio Manager servers are configured, logs from all servers will be included in the ZIP file.
    • The downloaded log files are those updated or created within the specified time window. However, each file may contain log entries from earlier periods.
    Tip: If you need logs for a specific issue, use a narrow time window to minimize file size and focus on relevant events.