Labeling helps you to manage your devices at scale. You can use labels to schedule, configure or query subset of the devices
Labels are used to:
- Filter your devices when searching for a particular group or a single device.
- During application deployment, as applications can provide a selector with a list of labels and their values.
Labels can be added to devices in several ways:
- Manually through API/CLI/dashboard.
- Through a registration token (when device is being provisioned).
- Automatically by the agent itself, if labels are found in the configuration directory.
Labels can be added (or removed) to devices either through the devices table or through the device details page:
Registration token labels can be edited in the provisioning page.
Once registration token labels are set, any new devices registering to the system will inherit them. You can modify registration token labels at any time, it will not affect existing devices.
Synpse allows devices to apply labels to themselves using a configuration file.
By default synpse looks for a labels configuration in
/etc/synpse/labelsfile. File format is
For example, a device with this file:
$ cat /etc/synpse/labels
You can use provisioning scripts to automatically update the
labelsfile. Any updates to it will automatically get sent to the Synpse controller.
You can filter your devices by using exact match, for example
labelKey:labelValueto get all devices that have this specific combination or just by specifying
labelKey:to list all devices that have
labelKeyin the their labels with any value.