Tags & Labels

what are tags & labels in factry historian, tags and labels are two separate but complementary ways of attaching metadata to your measurements docid\ xqwlemdcnfff3 0h gmms and calculations docid\ opiodkgnngyjedx6zkg d tags are written into the time series database together with each data point they are part of the underlying storage structure (e g in influxdb) labels are managed within factry historian itself they are used to group, filter, and organize data for data management, or forwarding why does it matter? both tags and labels help you make sense of your data at scale they enable you to filter or group measurements by metadata (such as product, location, or asset type) route specific subsets of data to external systems using forwarders docid\ td6emj3f 0xsgji7p4dag keep your system maintainable as your setup grows using tags and labels consistently allows you to manage hundreds or thousands of signals without relying on naming conventions alone how does it fit in the system? tags (tsdb level) tags are part of each data point in the time series database in influxdb, they are indexed key value pairs used for fast querying and grouping they are attached at write time , meaning they must be defined prior to the data being written example a temperature measurement might be stored with the following tags asset=line1 furnace unit=celsius phase=heating you can use these tags to filter data in dashboards or aggregate across a group labels (historian level) labels are maintained in factry historian and apply to measurements and calculations they are used to categorize data sets for easy management select subsets of data for forwarding to external systems using the forwarders docid\ td6emj3f 0xsgji7p4dag feature labels can be changed at any time without touching the underlying tsdb example you might apply these labels to a set of measurements energy team a forward to corporate these labels can then be used to filter while administering factry historian, or to selectively forward data example let’s say you have energy meters on five different lines each measurement is written with the following tags line=line x (with x from 1 to 5) inside factry historian, you assign labels to all five energy measurements energy forward to corporate you now have fast filtering by line or unit using tags centralized control over what gets forwarded to the corporate mqtt broker when you use it you use tags during data collection and ingestion for filtering and grouping in dashboards and queries to optimize time series queries on indexed fields you use labels to manage configuration and routing within factry historian to group signals by purpose, not just origin when using the forwarders feature to send specific sets of data to other systems common misconceptions tags and labels are not interchangeable tags live in the {{tsdb}} and are fixed once written labels are managed in the historian and can be updated at any time tags must be defined before data arrives labels can be applied later labels do not affect how data is stored in the tsdb, only how it is used and organized within the application best practices use tags for static metadata tied to the source of the data, such as asset, product use labels for categorization of data (e g energy, quality, process) apply labels consistently across similar measurements to make administration and forwarding easier more information creating and deleting labels docid\ mc0qkxew3eaffwrl94dxa configuring forwarders /#how does it fit in the system using labels