Configurations and Roles

Prev Next

SysTrack uses roles and configurations to control what data is collected, which automations run, and how monitored systems behave. Use factory roles, create custom roles, and build configurations tailored to your environment so each system receives the appropriate settings.

Video Transcript

Roles and configurations are a vital part of how SysTrack collects data and behaves in different computing environments.

A role is a set of rules or instructions. It tells SysTrack what data to monitor, when to trigger interactions, which automations to run, and many other scenarios. SysTrack offers two types of roles.

There are factory roles that define collection rules for common scenarios, such as systems with the same operating systems or systems that are virtual machines or servers.

Custom roles can also be created based on the use cases that are important to an organization. Perhaps a disk cleanup automation can be run whenever disk space hits 80% or higher, or additional data views need to be enabled for a dashboard to function properly. Maybe it wants to automate a health survey to check in with end users with struggling systems, or to create a notification when performance starts to falter.

A configuration is a collection of one or more roles. It defines how SysTrack behaves for a monitored system.

SysTrack provides a default configuration designed for typical users and systems. This SysTrack default configuration is a special case and does not contain any roles. It simply collects the standard set of data using default thresholds. The default configuration is assigned to all new monitored systems. That means that out of the box there are established data collection rules, thresholds, enabled features, and group policies.

However, because no two environments are alike, and because that SysTrack default configuration will be reset to the factory settings whenever the SysTrack agent is upgraded, you should create your own custom configurations based on use cases in your environment. These custom configurations can contain factory roles, custom roles, or both.

Finally, the appropriate configurations are assigned to systems. Each system can have only one configuration assigned.