Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InfluxDB migration to backend data source #43076

Closed
9 tasks done
joey-grafana opened this issue Dec 14, 2021 · 3 comments
Closed
9 tasks done

InfluxDB migration to backend data source #43076

joey-grafana opened this issue Dec 14, 2021 · 3 comments
Assignees
Labels
datasource/InfluxDB type/epic Issue made of smaller issues

Comments

@joey-grafana
Copy link
Contributor

joey-grafana commented Dec 14, 2021

Checklist:

@gtk-grafana
Copy link
Contributor

Closing as this looks completed.

@kylebrandt
Copy link
Contributor

@gtk-grafana (@itsmylife)

So this isn't complete. There are two different things:

Migrating datasource to the backend makes it so the backend is what takes a query model, and turns into an API request, and in the dataquery case turns the response for the into dataframes. This makes things consistent with alerting and FE queries instead of doing it twice - enables server side query caching etc.

So currently the backend migration (what this issue is about) is under the feature flag influxdbBackendMigration so it has not been shipped. It is also perhaps not complete as far as what needs to be done under the feature flag -- not sure.

@itsmylife
Copy link
Contributor

I am closing this issue since it is completed. This was phase 1 of the migration. Phase 2 is here #60321

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datasource/InfluxDB type/epic Issue made of smaller issues
Projects
None yet
Development

No branches or pull requests

5 participants