Tags are a flexible and powerful way for organizing and labeling your assets within TagoIO, allowing you manage access and identify key components such as Devices, Actions, Analysis, Dashboards, Users & Access rules.
Operating like key-value pairs, tags enable you to assign relevant metadata such as names, descriptions, categories, locations, customers, products, and more, to your assets.
Tags can be assigned to a wide range of components within TagoIO, and are typically accessible through a designated "Tag" tab when configuring assets that support label assignment
Each tag have 2 configurable parameters:
Key: name of the parameter used as reference, you can also select an existing key.
Value: the value of the parameter that you want to assign to your asset.
The main usage of tags is to identify and manage access of the assets. For instance, you can filter out the assets by using API List endpoints or SDK methods and get a list of devices that belong to a specific customer or product by using the tag filter parameter.
Check out our API and SDK documentation.
The maximum number of Tags per asset is 30.
If you attempt to add additional items beyond the limit, a notification will appear indicating that the maximum capacity has been reached.
2. Where to use
You can set your tags in different ways depending on your application design. Here are some TagoIO features that make extensive use of this system:
2.1. Access Management
You can use tags to manage access from users to devices, dashboards and even other users. This allows for scalability and easy management of access rules. For example, you can create a user group with a tag like `role: Manager` and grant them access to all devices with the tag `customer: ACME Inc.`.
2.2. Blueprint Dashboards
This dashboard utilizes tags to enable users to seamlessly switch between devices that provide data to the dashboard. By incorporating tag-based functionality, the dashboard can be used across multiple devices, making it a highly versatile and flexible tool. The dashboard identifies selectable groups of devices based on their assigned tags, enabling users to quickly and easily switch between data sources as needed.
For example, you can create a blueprint dashboard with a tag like `device_type: Temperature Sensor` and allow users to choose any device with that tag from a dropdown menu.
Tags can be managed from different sources:
TagoIO Interface: You can manually add or edit tags from the TagoIO interface by clicking on the asset and then on the Tags tab.
Analysis SDK: You can programmatically add or edit tags from an analysis script by using the SDK methods available for each asset type. For example, you can use `account.devices.edit()` or `account.actions.edit()` methods.
TagoIO API: You can also use the REST API endpoints for each asset type to add or edit tags by sending HTTP requests with JSON payloads containing the tag information.
You can group related dashboards using dashboard tags. To do so, go to “Dashboard”, click on the gear icon to edit it, then on the section “Tags” create a new tag. After that, on the section “Group dashboards using Tags” select the grouping tag. To ...
Blueprint Devices are dynamic Devices available on Blueprint Dashboards. They can be changed by the user in realtime, and by doing so, the Dashboard will reload the data for the Widgets that use them. You can change the Blueprint Devices by selecting ...
Rate Limits (Hard limits)
When executing requests to TagoIO, you will have a limit on the number of requests that can be made during a certain time period. These limits are applied in short intervals every minute, allowing us to provide a reliable and scalable API that our ...
Table widgets present your data in a tabular way. You can also allow users to change values on the cells, delete rows, and more. There are two types available: the Static Table, Dynamic Table and the Device List. Static Table It is one of the special ...
Each end-user that is added in the User Management list is counted as an end-user. End-users, also called RUN-users, can be automatically added when they sign up in your RUN application. If any of your profile reaches the limit of end-users ...