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
What would you like to be added:
A property added to FieldConfig, that instructs consumers that they can/should extract dimensions (create labels) from the field name.
Why is this needed:
Some data is like this, in SSE (so it works with alerting and Recorded Queries), we have a hack that does this (somehow?) if the DS Type matches (Currently Graphite, but adding Dynatrace soon.
Adding this as a FieldConfig:
allows control of this behavior to belong to the data source which better understands the data
Allows DS authors to apply this only to certain responses (more fine grained)
Easier to debug since the frame will declare that the data can be treated this way
vNext could include an additional property that guides how to extract dimensions/labels, (e.g. { "delim": ".", "keys": ["metric", "namespace", "pod"] }.
(Maybe Frame Meta could work as well if want applied to all numeric fields perhaps, depends on how fine grained we want the control - frame wide or field specific)
I like the idea. But in practice, ds authors don't know the mapping of the fields. Also It will be tiresome for a customer to enter all the field mapping manually. for every metric this will be different even though they may be of same length.
What would you like to be added:
A property added to FieldConfig, that instructs consumers that they can/should extract dimensions (create labels) from the field name.
Why is this needed:
Some data is like this, in SSE (so it works with alerting and Recorded Queries), we have a hack that does this (somehow?) if the DS Type matches (Currently Graphite, but adding Dynatrace soon.
Adding this as a FieldConfig:
vNext could include an additional property that guides how to extract dimensions/labels, (e.g.
{ "delim": ".", "keys": ["metric", "namespace", "pod"] }
.Reference: grafana/grafana#90246 (comment)
cc @yuri-tceretian @yesoreyeram @ryantxu
The text was updated successfully, but these errors were encountered: