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

Docs: Add additional step/check to the Loki HELM Migration Guide for checking Schema Config #9394

Open
SeamusGrafana opened this issue May 4, 2023 · 1 comment
Assignees
Labels
help wanted We would love help on these issues. Please come help us! type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories

Comments

@SeamusGrafana
Copy link
Contributor

For the Loki HELM Migration Guide it would be beneficial to add an additional step/check into this, for the user to verify the Schema Config has been set correctly in the new HELM Chart Config, and any old Schema Configs are migrated over correctly.

This helps when users have multiple schemas that were used before of different values to those specified in the loki HELM Chart. Items to check should include, a correct from date, store, schema and index prefix etc.

Link to Doc: https://grafana.com/docs/loki/latest/installation/helm/migrate-from-distributed/

Relevant Context: https://github.com/grafana/support-escalations/issues/5824

@SeamusGrafana SeamusGrafana added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label May 4, 2023
@trevorwhitney
Copy link
Collaborator

I think the ideal solution here is to mention they should not change the schema when also doing a migration. Do the migration first, then upgrade the schema in the new cluster only.

Upgrading schemas and doing migrations are both complicated, do one at a time.

@JStickler JStickler added the help wanted We would love help on these issues. Please come help us! label Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted We would love help on these issues. Please come help us! type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

No branches or pull requests

3 participants