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
While Falcon LogScale support live query, the native UI handle it efficiently by breaking down a query to static query and live query, when static query part complete, the front-end only poll the live query for new data coming in. Current FalconLogScale datasource does not support that as far as I know.
So in a real environment, user often set the time-range in dashboard, and enable auto-refresh, this can impose very high load on LogScale backend, since the auto-refresh will trigger the entire query resubmitted, with different time range(e.g: 30s refresh will shift the start and end time by 30s), this is considered a brand new query in LogScale backend. We are seeing backend query job grow exponentially when just a small set of users are using Grafana dashboard with some panels have LogScale planel with auto-refresh enabled.
It's hard to ask user to not to use auto-refresh in Grafana dashboard. One possible solution would be to allow an option in datasource config to ignore dashboard auto-refresh setting, and with an indicator in the panel to tell user the auto-refresh is disable for the panel that's using that specific data source?
For long-term, it would be nicer to add the live query support for the datasource, so when auto-refresh is enabled, the datasource would be running live query in the backend?
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
-
While Falcon LogScale support live query, the native UI handle it efficiently by breaking down a query to static query and live query, when static query part complete, the front-end only poll the live query for new data coming in. Current FalconLogScale datasource does not support that as far as I know.
So in a real environment, user often set the time-range in dashboard, and enable auto-refresh, this can impose very high load on LogScale backend, since the auto-refresh will trigger the entire query resubmitted, with different time range(e.g: 30s refresh will shift the start and end time by 30s), this is considered a brand new query in LogScale backend. We are seeing backend query job grow exponentially when just a small set of users are using Grafana dashboard with some panels have LogScale planel with auto-refresh enabled.
It's hard to ask user to not to use auto-refresh in Grafana dashboard. One possible solution would be to allow an option in datasource config to ignore dashboard auto-refresh setting, and with an indicator in the panel to tell user the auto-refresh is disable for the panel that's using that specific data source?
For long-term, it would be nicer to add the live query support for the datasource, so when auto-refresh is enabled, the datasource would be running live query in the backend?
Beta Was this translation helpful? Give feedback.
All reactions