Skip to content

Automation Script Log

Purpose

The Automation Script Log shows the results of the automation scripts that runbook tasks run, one row per VM, newest first. Its on-screen subtitle reads: "Results of automation scripts, one row per VM, newest first. Written by scripts and runbooks; read-only here."

Use it to check what a script did to a VM during a migration: whether it succeeded, the one-line summary, and the script's full output. Nothing on this screen can be created, edited or deleted.

The Automation Script Log is one of four screens under Logging. Field-level data changes are in the Change Log, business workflow events and sign-ins are in the Activity Log, and system and diagnostic messages are in the Event Log.

Where to find it

Logging → Automation Script Log

What you see

Columns

  • Time Stamp
  • Vm Name: the VM the script ran against.
  • Runbook Task Name: the runbook task that ran the script, for example a post-cutover target check.
  • Package Id
  • Status: for example Success or Failed, with a tick or cross icon.
  • Message: a one-line summary of what the script did.
  • Output: the script's structured output, for example JSON or a playbook log.
  • Move Group

Filters

Each column has a filter row, there is a Search: box, and the page-size selector offers 10, 25, 50 or All entries per page.

Actions

The grid toolbar has a back arrow and a download icon. There is no Create New, Edit or Remove selected: the grid is read-only.

How to

Check what a script did to a VM

  1. Go to Logging → Automation Script Log.
  2. In the Vm Name filter, enter the VM's name.
  3. Read Status and Message on each row, newest first.
  4. For the detail, read Output on the row.

Find failed script runs

  1. Go to Logging → Automation Script Log.
  2. In the Status filter, enter Failed.
  3. Read Runbook Task Name and Message to see which task failed and why.