Tagging Stages

During onboarding, we complete tagging in two stages:

Stage 1: Onboarding Tagging

During onboarding, we deploy all tags to resources with a value of zero (0). When a tag is set to zero (0), no agents are deployed.

The environment is now ready for tags to be changed to their desired state for Business as Usual (BaU).

Stage 2: Business as Usual (BaU) Tagging

Business as Usual (BaU) tagging makes sure that all new resources get the default tag for each service. This makes sure that all machines are patched and/or backed up by default.

BaU tag values can be customised on a per account basis.

During BaU, the procedure is:

Every hour: Machines are tagged with a service module Specific Key : Value pairs, for example, the Patching Tag can have a Key : Value pair of swoPatch : 2.
Once a day: Tags are automatically evaluated and agents are pushed out according to the tag value, for example, the tag swoPatch : 2 initiates a Patching Agent installation and aligns in to Patch wave 2.

At the point of installation, the agents register automatically with SoftwareOne tooling, configured according to the tag value.

Tag Definitions

The following table provides a view of the value definitions for tags during Onboarding and BaU.

Tag key	Recommended BaU tag value	Agent installation values	Tag value definition
swoBackup	1	1	0 = No backup 1 = Backup with Plan 1 2 = Backup with Plan 2
swoPatch	2	0	0 = No patch 1 = Patch Wave 1 2 = Patch Wave 2 3 = Patch wave 3 Runs at agent time.
swoMonitor	1	1	0 = No Monitor 1 = Agent monitoring 2 = API Monitoring

Related Information

For more information about the tagging, refer to Tagging Resources.