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
It would be awesome if there was an option to enable fill unavailable fields with null. This way it would be possible to visualize data that contains variable fields. The background is, some Api implementers prefer to not send the key with value null if the value is unset. One possible usecase is effective bandwidth reduction.
The text was updated successfully, but these errors were encountered:
Some sort of time scaffolding function would work well. For instance, "scaffold to 5-second generated time series". You would then have options like "interpolate" leave null or whatever for missing values.
A nice feature of JSONata can mitigate your (and mine) problem. It performs an existance test for each entry and it is well managed by grafana.
$.doc.($exists(channel) ? channel : null)
You can also use it as something fancier like $.doc.(channel > 5 ? "great" : "bad")
Hope it helps. Btw, I massively use this feature and its verbosity bothers me quite a lot.
So any embedded option to automatically fill fields as you propose would be great.
My JSON server has a parameter to limit the number of channels to return (rtd_len) and the number of datapoints (samples), currently I get an error when I configure less channels than provided in the fields specification, while the query result looks fine with rtd_len=3, samples=10:
With all specified fields (rtd_len=4), I do get all channels:
Ignoring empty fields by setting it them to null will certainly help to toggle showing last channel (Neutral current in my case).
It would be awesome if there was an option to enable fill unavailable fields with null. This way it would be possible to visualize data that contains variable fields. The background is, some Api implementers prefer to not send the key with value null if the value is unset. One possible usecase is effective bandwidth reduction.
The text was updated successfully, but these errors were encountered: