Logs - Automate_Studio_Manager - Latest

Automate Studio Manager Guide

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio Manager
Version
Latest
Language
English
Product name
Automate Studio Manager
Title
Automate Studio Manager Guide
Copyright
2024
First publish date
2018
Last updated
2024-07-22
Published on
2024-07-22T13:20:59.472887

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.

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.

Logs - Process

  1. Go to Settings > Logs.
  2. 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 greatest impact on performance.

  3. Define the maximum log file size in MB in the File Size field (example: 10 MB). Logs larger than the size specified roll over to the next log file.
  4. 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. 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.
  5. Specify the destination path in the Destination Path for Log Files.
  6. Click Save.