Setting up a Monitoring and Maintenance Agreement

Once you have ordered your new Monitoring and Maintenance Agreement (MMA) and it has been configured for use in the backend, its status will be "Waiting Agent" and ready for you to install the required monitoring agent software.

The details in this article will help you to run the necessary commands that will download a management install script to your server and then run that script - with your specific details included.
This will register your server in our automation, management and monitoring systems.

$ ping salt-master.servercontrol.com.au
PING salt-master.servercontrol.com.au (117.120.8.35): 56 data bytes
64 bytes from 117.120.8.35: icmp_seq=0 ttl=62 time=18.711 ms
64 bytes from 117.120.8.35: icmp_seq=1 ttl=62 time=18.590 ms
64 bytes from 117.120.8.35: icmp_seq=2 ttl=62 time=17.221 ms

yum install curl wget

yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm

sudo apt update
sudo apt install curl wget

First, you will need to be logged into your MySAU account.

Click on the "Services" link on the left sidebar.

Then click on the Management link near the top right of your screen.

Any Monitoring and Maintenance Agreement (MMA) you have will show towards the bottom of this page.
If you have more than one, they will be on separate lines.
Each will have the Monitored server/VM name on each line, with three dots for the actions on the right-hand side.

Click the three dots on the right end of the relevant line to display more options.

Click on the "View Setup Instructions" link.

A new window will appear with the required command for either Linux or Windows, you will see slightly different details to what is shown in this example.
You can use the "Copy" link on the right side of the command for your relevant Server/VM or manually copy the command in your web browser.

Then you can paste the required command into an SSH session for Linux or a PowerShell window for Windows.
The account you use for login to run these commands must have root/admin privileges.

About 5-10 minutes after you have successfully run the command on your server, the status for your monitored server should change to Active, confirming the integration process is complete.