Tagging Resources for Monitoring
We apply tagging to your instances to capture them and the services running on them for inclusion in our Monitoring service. Tagging lets you assign metadata to resources in the form of tags. Each tag is a simple label consisting of a user or SoftwareOne-defined key and an optional value that can make it easier to manage, search for, and filter resources. Tags can be applied individually on the source server level. Each tag applied on the server level is assigned to the target instance and the storage volume(s) attached to that instance.
For example, to distinguish between business critical resources and non-critical resources, you can make sure that the monitoring of business critical resources is handled with a higher severity by setting the value of the Risk Class tag, where the value of the swoRiskClass tag is set to 2. You can switch-off monitoring a resource, by changing the value of the Monitor tag, where the value of the swoMonitor tag is set to 0.
The following table provides information about the tagging and values that we apply to your resources, to include them in, or exclude them from the Monitoring service.
Tag | Description |
swoMonitor | Used to identify if a resource is, or is not monitored by SoftwareOne, and the type of monitoring to apply. Possible values: 0–Do not monitor this system. |
swoRiskClass | Used to identify the risk and/or criticality of a resource. Possible values: 1–Identifies that the resource is critical (high risk), for Production resources. 2–Identifies that the resource is non-critical, for non-production resources. |