You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These 2 groups of fields seem remarkably similar, and I'm not sure which to use. are both needed? It seems that at least for Target.Group vs Target.GroupBy, the former has a little more type safety, but is a little clunkier to use. It seems also that if I declare a Tag to group on, it does not end up in the query, while it does show up in the panel JSON:
{
"params": [
"k8s_cluster"
],
"type": "tag"
},
Query: ... GROUP BY time(1s) fill(null)
For Target.Alias vs Target.AliasBy, I don't know if it's working properly, because the legend does not show the series breakdown in the legend. Again, the syntax of these two is different, but the effect seems to be the same in the panel JSON, though it doesn't seem to make a difference in the query. "aliasBy": "$tag_k8s_cluster" in the panel JSON has no effect on the query for the panel.
The text was updated successfully, but these errors were encountered:
Unfortunately but Grafana doesn't have a strict schema for dashboards so the answer probably depends on which version you are using. We've had plans to separate fields according to major Grafana versions but it never came to fruition.
These 2 groups of fields seem remarkably similar, and I'm not sure which to use. are both needed? It seems that at least for
Target.Group
vsTarget.GroupBy
, the former has a little more type safety, but is a little clunkier to use. It seems also that if I declare a Tag to group on, it does not end up in the query, while it does show up in the panel JSON:Query:
... GROUP BY time(1s) fill(null)
For
Target.Alias
vsTarget.AliasBy
, I don't know if it's working properly, because the legend does not show the series breakdown in the legend. Again, the syntax of these two is different, but the effect seems to be the same in the panel JSON, though it doesn't seem to make a difference in the query."aliasBy": "$tag_k8s_cluster"
in the panel JSON has no effect on the query for the panel.The text was updated successfully, but these errors were encountered: