Supervisions
Supervisions are a device monitoring tool. They are used to monitor the values of multiple devices configurations and states. They can be created from the built-in front-end, or through the API.
Creating a supervision requires providing the following information: - A name to identify the supervision. - A list of devices to monitor. - Target tenant: only devices in this tenant can be monitored. - Configurations and states to monitor, by providing key and values for each one.
Info
Note that creating a supervision will not impact the devices, their configuration will not be altered by it. When needing to update multiple devices configuration, use campaigns instead.
Features
Supervisions can provide multiple indicators: - A list of devices with their current and expected states and configurations. - The percentage of devices with valid states and configurations. - The repartition of values for each key.
Devices can also be filtered by name and success status.
Monitoring a state for a specific key does not require monitoring a configuration with the same key. The opposite is also true. When both are specified, they do not need to have the same value. For example, it is possible to use this configuration:
| Key | State | Configuration |
|---|---|---|
| firmware_version | 1.1 | 1.1 |
| assets_url | - | https://my-assets.com |
| update_state | completed | - |
| task_completed | false | true |
Lifecycle
Supervisions do not have an end date, they will stay open until they are deleted by a principal. Once created, they can be edited to change the device list or their monitored states and configurations.