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 seems that this might give a way to enable influxDB queries, either as a function (or one of a few) in a yaml file, or in your base code itself. I'm still on V1 of influxDB (as is the link), so I don't use FLUX queries, yet.
The use case is to look back further in time than the recorder DB supports for interval data. Note: a single trace that could use interval data then switch to statistics data for the balance of the period would be useful as well.
Still, influxDB would be nice. I can see developing queries in Grafana, and sticking them into a Plotly yaml file. See, I hope not to deploy both Plotly and Grafana visualizations. ;) My influxDB is mostly just sitting there now.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It seems that this might give a way to enable influxDB queries, either as a function (or one of a few) in a yaml file, or in your base code itself. I'm still on V1 of influxDB (as is the link), so I don't use FLUX queries, yet.
The use case is to look back further in time than the recorder DB supports for interval data. Note: a single trace that could use interval data then switch to statistics data for the balance of the period would be useful as well.
Still, influxDB would be nice. I can see developing queries in Grafana, and sticking them into a Plotly yaml file. See, I hope not to deploy both Plotly and Grafana visualizations. ;) My influxDB is mostly just sitting there now.
Beta Was this translation helpful? Give feedback.
All reactions