CDA Logging Files

Log files help you track the events that happen when CDA is running.

Location

Log files are saved by default in the logs subfolder of the WebUI folder (e.g. c:\Automic\Release.Manager\WebUI\logs\)

File Generation

Every day at midnight new files will be created with default names and a date suffix will be appended to the existing log files. For example, log.txt will be renamed to log.txt.2020.03.04.

File Types

The logs folder contains the following files:

  • log.txt

    Main log of the application. It contains the following information:

    • General system information:

      • System start date and time

        Example: 2020-04-16 13:06:49,608

      • Version

        Example: 10.0.3+build.25191

      • Environment processor

        Example: 64bits

      • Timezone information:

        • Standard time name.

          Example: W. Europe Standard Time

        • Daylight saving time name (optional).

          Example: W. Europe Daylight Time

        • Current date and time.

          Example: 4/16/2020 1:06:49 PM

        • Coordinated Universal Time.

          Example: 4/16/2020 11:06:49 AM

        • UTC offset.

          Example: 02:00:00

      • System configuration:

        • SystemMonitor
        • Application
        • Deployment
        • DeploymentCalendars
        • CustomerAppSettings

        For more information, see: Configuring CDA via Customer.Config File

      • Connections:

        • System

          The system user is required by the CDA server to communicate with the Automation Engine. It must have administrator rights.

          Example: User: 100/USER/USER; Client: 100

        • CP

          Example: AEServer.local:2217

        • Connection

          Example: Name: AUTOMIC; System: AUTOMIC

        • Queue trigger

          Example: Agent: WIN01; Login: LOGIN.WIN01

        • Connection strings

          • MainDatabase
          • DB Versions

            List of all CDA database versions found in the system. They must be compatible with the CDA server version.

            Example: DB Versions: 1002201912181; 1000201908301; 1000201905311...214201208151

      • Events coming from:

        • RM.TenantConfig (SMTPServer, notifications, reservations, global definitions, approval requests, deployment calendars, etc...)
        • UI.Calendar
        • RM.Heartbeat
        • RM.AdminConnect
        • Ventum.Bond2.Services.Impl.SsoService (single sign on management)
        • Ventum.Bond2.Timezone.BaseTimeZoneProvider
        • RM.AdminConnect
        • Ventum.Bond2.Services.Telemetry.Impl.TelemetryCollector (Telemetry)
        • RM.AEInterop (Login objects, credentials)
        • Ventum.Bond2.Web.Widgets.DynamicProperty.DynamicPropertyController (dynamic properties)
        • Admin CLI (index data management)
  • Operation.txt

    CDA servers operating in the CDA system.

    • Host name

      Example: MYHOSTNAME

    • Instance ID

      Example: 51rf0a1b-68d9-4e3s-983d-92t2rae82874

    • Role

      Options: primary executor, other.

      Note: The primary executor role is automatically granted.

  • Setup.txt

    Log of application setup (e.g. through OneInstaller or System/Setup API).

  • DataAPI.txt

    Log for import/export.