What are Automations

Introduction

Automations allow you to execute a set of custom tasks, each of these automations can be configured to repeat or run on a schedule, or even just to run manually. The Automation tasks that are available will vary based on the Hypersocket product that is in use but can include sending emails, block and unblocking IP addresses, stopping and restarting the server, configuration changes, user management, scripts and much more.

Creating an Automation

Each automation task has a set of options that allow you to customise its behaviour. As an example we will create a Send Email Automation that sends the log files to a specified user each night.

When the Automation dialog first displays it only shows two fields. When you select a Task the dialog will display further task properties as well as the schedule options. After selecting Send Email in the task list we can now set the subject and body of the email, set alternative HTML, add attachments, and set the delivery details, along with the standard Automation options of setting a schedule and repeating specifications.

First we set the Subject and Body.

The Delivery tab allows us to specify the user(s) that should receive the email, in this case we are just adding an administrator account.

In the Attachments tab we can specify the local location of the log files that we wish to send with the email, you can also upload files that should be send out with automations. You can amend the name of the file when it is attached by placing a filename in the second field.

And in the Schedule and Repeat tabs we set when and how often this email will be sent, in this case the email is set at 11:59pm each day until the Automation is cancelled.

Once configured the Automation will run automatically on the configured schedule until it is changed or removed.

Automations can currently be set for the following actions, each of these have their own options for configuration:

  • Block IP Address
  • Copy File
  • Copy Folder
  • Create Folder
  • Delete File
  • Delete Folder
  • Execute Command
  • Monitor TCP Port
  • Move File of Folder
  • Resolve IP Address
  • Restart Server
  • Resume User
  • Send Email
  • Shutdown Server
  • Suspend User
  • Touch File
  • Truncate File
  • Unblock IP Address

 

Chaining Automations

It is possible to configure an existing Automation to run additional actions once it has completed, whether in success or failure. Select one of the Automations and below the list you will see a box representing the selected item, this is the beginning of the automation flow. In this example I've selected the System Logs automation that emails the logs to the administrator.

Selecting the  icon in the display will present a new Create Automation page that now includes two new options, Triggers On and Triggers Task.

Provide a name for the new task and then specify the triggers that will happen, in this case we'll make an automation that copies the log file to a new location after the email has been sent.

After saving the new task the process flow for "System Logs" now appears as below, indicating that when System Logs is run Copy logs will follow.

 

We can continue to add more automations to this process to create a full automated process for jobs that we want to perform, for example the image below shows a full process that takes a copy of both logs files that are emailed, copies these to a location and transfers them to another server, then deletes the copies of the files before sending another email to the admin notifying them that the logs have been backed up off system.

Have more questions? Submit a request

Comments