As a customer of Techs+Together, you should to be aware that your tenancy is a partition on a SaaS server. Each tenant has their own partition, but we all share hardware. 

So when using the VSA, you need to keep it in mind and we ask you to “play nicely” with others. 

 

Some activities within the VSA can cause quite a bit of pressure on the resources, such as audits, scans, patching, etc. 

This is where the distribution window comes into play. 

Whenever you are running something on multiple machines, please set your distribution window accordingly. Our recommendation is that for every 50 machines you run something on, you should set your distribution window to minimum of 15 minutes. 

 

Also, when using monitor sets and setting the sample interval, you need to keep in mind that the more monitor sets you add, the more important the sample interval becomes  because the more resources will get consumed. 

 

One of the most resource intense activities that we ask you not to perform, as it is meant for On Prem servers is setting anything up in the Agent module under Event Log Settings. This functionality copies all the settings to the server, and because we are SaaS, it can cause major performance issues in the VSA not only for you, but also for other tenants. Monitoring of the event logs for Event IDs  can be done in the Monitor module under Event Log Alerts.

 

One more thing worth mentioning here is the Update Lists by Scan feature in the Monitor module. This also tends to consume a lot of resources as it scans machines for all counters, services, and event log types. 

 

If in doubt, you can always refer to the pre-recorded sessions of our Getting Started with Kaseya VSA webinar where we mention these spots in the VSA that are to be used with caution. The webinars can be found on our website here: https://techstogether.com/allthings/ or you can contact us at service@techstogether.com.