Skip to main content

ProVal Script Detailed Report

Summary

This document provides a detailed overview of all custom scripts built by ProVal along with their implementation status information.

Columns

ColumnDescription
Script NameScript name
Script NatureIndicates whether the script is "ProVal Client Specific," "ProVal Deprecated," or a ProVal non-stack script.
Script TypeIndicates whether the script is a Computer or a Client script.
Script NotesContains brief notes providing an overview of the script.
Function ScriptIndicates whether the script is a function script that can only be called by automation or cannot be run manually. 0 - Not a function script; 1 - Function script.
Scheduled ScriptIndicates whether the script is scheduled or not. 1 - Scheduled; 0 - Not Scheduled.
Scheduled ByShows the name of the Automate user who scheduled the script.
Total RunsThe total count of script runs overall, depending on the script retention set in the environment.
Run Last 30 DaysContains the script execution counts in the last 30 days overall.
First Run DateContains information on the script's first run date.
Last Run DateContains details of when the script was last executed.
Last Scheduled RunContains information on the last scheduled run date of the script, either manually or via a group.
Next Scheduled RunShows the next upcoming script execution date.
Total Scheduled RunShows the number of schedules set for the script in the environment.
Average Run TimeIndicates the average run time of the script in seconds.
Group ScheduledDenotes the name of the group where the script is scheduled.
Group PathShows the group's full path where the script is scheduled.
Limit SearchIndicates if the script is bound to a search or not. 1 - Limited to search; 2 - Applied to all members of the group.
Search NameShows the search name to which the script is limited.
# Remote MonitorDisplays the total number of remote monitors where the script is used as an autofix.
# Internal MonitorDisplays the total number of internal monitors where the script is used as an autofix.
Applied to Alert TemplateIndicates whether the script is bound to an alert template or not. 1 - Yes; 0 - No.
Alert TemplateContains the alert template name to which the script is bound to run.
Machines AffectedShows the count of computers to which the script is scheduled.
In UseIndicates whether the script has been run within the past 6 months, is actively scheduled, or applied to any remote or internal monitors. Marks Yes or No if the above conditions are met.
Scheduled in Past 6 MonthsShows which script was either run by the group or manually in the past 6 months, or if the script was running as an autofix via monitors. If any condition is met, it is marked as "Recently Added."

Color Coding

Color coding is applied to the columns "# Internal Monitor," "# Remote Monitor," "Script Nature," "Group Scheduled," "Scheduled in Past 6 Months," and "Synced/Updated" as shown below:

Color Coding

  • # Internal Monitor: Highlights counts greater than 0 to indicate how many internal monitors the script was applied to.
  • # Remote Monitor: Highlights counts greater than 0 to indicate how many remote monitors the script was applied to.
  • Script Nature: Highlights "Deprecated ProVal Script" in red and "Client-Specific ProVal Script" in red to draw attention to where the "ProVal" scripts are non-stack ProVal scripts.
  • Synced/Updated: Highlights "Yes" in green, "No" in orange, "Client-Specific" in grey, and "Deprecated" in red to easily show whether the script is deprecated, client-specific, or if a non-stack script is properly synced/updated from the ProVal plugin.
  • Group Scheduled: Highlights the group full name in green to indicate where the script is scheduled.
  • Scheduled in Past 6 Months: Highlights "Recently Added" in green to show which script was either run by the group or manually in the past 6 months, or if the script was running as an autofix via monitors. If any condition is met, it is marked as "Recently Added."