-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
cephadm: change loki/promtail default image tags #57164
Conversation
@aaSharma14 FYI |
Hey @aaSharma14 , I took a look at this, 3.0.0 uses new schema v13 with new structured metadata, it implies migrating from BoltDB with v11 schema to tsdb with v13 schema. We currently have: schema_config:
configs:
- from: 2020-10-24
store: boltdb-shipper
object_store: filesystem
schema: v11
index:
prefix: index_
period: 24h We would need to add something like following: schema_config:
configs:
- from: 20YY-MM-DD
store: tsdb
object_store: filesystem
schema: v13
index:
prefix: index_
period: 24h Another option is starting loki with
|
71ceb0b
to
649213c
Compare
jenkins test make check |
This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved |
This commit changes the default images for both loki and promtail containers. Also, to allow this update we need to update the configuration of loki in order to add a new storage schema configuration: ``` - from: 2024-05-03 store: tsdb object_store: filesystem schema: v13 index: prefix: index_ period: 24h ``` This is because 3.0.0 uses new structured metadata. See [1][2]. [1] https://grafana.com/docs/loki/latest/operations/storage/schema/ [2] https://grafana.com/docs/loki/latest/get-started/labels/structured-metadata/#when-to-use-structured-metadata Fixes: https://tracker.ceph.com/issues/65784 Signed-off-by: Guillaume Abrioux <gabrioux@ibm.com>
This commit changes the default images for both loki and promtail
containers.
Also, to allow this update we need to update the configuration of loki
in order to add a new storage schema configuration:
This is because 3.0.0 uses new structured metadata.
See [1][2].
[1] https://grafana.com/docs/loki/latest/operations/storage/schema/
[2] https://grafana.com/docs/loki/latest/get-started/labels/structured-metadata/#when-to-use-structured-metadata
Fixes: https://tracker.ceph.com/issues/65784
Signed-off-by: Guillaume Abrioux gabrioux@ibm.com