tags¶
Description¶
Used to specify tags to publish a metric dataset. You can only specify a regular column or a link column as a tag when publishing a metric dataset using make_metric. If a link column is set using a nested JSON subpath, the tag function will not accept such link column as a valid tag.
Return type¶
grouping
Domain¶
This is a scalar function (calculates a single output value for a single input row.)
Categories¶
Usage¶
tags([ grouping_1, grouping_2, ... ])
Argument |
Type |
Optional |
Repeatable |
Restrictions |
|---|---|---|---|---|
grouping |
storable |
yes |
yes |
column |
Examples¶
make_metric metric_1, tags()
No tags have been provided so this metric dataset will be established without tags, while having the metric and value columns populated with a metric called metric_1.
make_metric metric_1, metric_2, tags(podName, ^Cluster...)
Let’s say the Cluster link column is set from the clusterUid and clusterName column. As a result, the tags will be podName, clusterUid, and clusterName columns, while the metric and value columns are populated with twos metrics called metric_1 and metric_2.
make_metric metric_1, tags(^Cluster...)
Let’s say the Cluster link column is set from attributes.clusterUid and attributes.clusterName. Since this link column is set using nested JSON subpath, it will be rejected by the tags function and request the user to set the Cluster link using regular columns.