You will notice that the Overview screen makes reference to Criticality in various views. By default, the value of device criticality is set to Undefined. Device criticality is intended as a mechanism for classifying endpoints into degrees of criticality, or importance. For example, endpoints which support mission-critical functionality within an organisation can be classified appropriately. This allows you to manage devices based on criteria you define, associated with their criticality.
Device criticality is an attribute of a device that defines its importance within an organisation. As defined by default in Tachyon, criticality has the following default settings
- Undefined (or not set).
At present, device criticality is not directly used by Guaranteed State, though you can define it and view it.
Tachyon also supports the use of the criticality setting when defining coverage for an instruction. For example, you can choose to target an instruction to be sent only to devices whose criticality is set to any state except Critical.
Setting Device Criticality
Device criticality is set using the instruction 1E-Explorer-TachyonAgent-SetCriticality to set device criticality.
From the Tachyon Explorer, enter: Set the criticality of my devices.
Select the instruction and then choose the desired criticality from the dropdown.
Select the coverage for the instruction. Then submit it. After approval, devices which match the specified coverage value will have their criticality set to the specified value.