The boltdb-shipper store in scheme-config is deprecated and will be removed in Loki 4.0. This commit adds an opt-in to move to TSDB.
Setting LOKI_TSDB_FROM_DATE in <app>.env adds a second schema_config period with the TSDB store from that date onward, alongside the existing boltdb-shipper, so logs before the cutover stay queryable under the old store while new logs are indexed with TSDB.
It's important to pick a future day for LOKI_TSDB_FROM_DATE, e.g. the day after you first deploy this env: Both stores share the same
per-day table, so a past or same-day date makes them collide over that day's data and breaks querying it.
The boltdb-shipper store in scheme-config is deprecated and will be removed in Loki 4.0. This commit adds an opt-in to move to TSDB.
Setting `LOKI_TSDB_FROM_DATE` in `<app>.env` adds a second schema_config period with the TSDB store from that date onward, alongside the existing boltdb-shipper, so logs before the cutover stay queryable under the old store while new logs are indexed with TSDB.
It's important to pick a future day for `LOKI_TSDB_FROM_DATE`, e.g. the day after you first deploy this env: Both stores share the same
per-day table, so a past or same-day date makes them collide over that day's data and breaks querying it.
boltdb-shipper is deprecated and will be removed in Loki 4.0.
Setting LOKI_TSDB_FROM_DATE adds a second schema_config period (store:
tsdb) from that date onward, alongside the existing boltdb-shipper
period, so logs before the cutover stay queryable under the old store
while new logs are indexed with TSDB.
CODEOWNERS rules
requested review from monitoring-ng-maintainers 2026-10-29 12:00:48 +00:00
looks good! i haven't had time to properly test loki yet. are you running it? i had to do some changes for getting it to start but i couldn't commit them yet.
looks good! i haven't had time to properly test loki yet. are you running it? i had to do some changes for getting it to start but i couldn't commit them yet.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The boltdb-shipper store in scheme-config is deprecated and will be removed in Loki 4.0. This commit adds an opt-in to move to TSDB.
Setting
LOKI_TSDB_FROM_DATEin<app>.envadds a second schema_config period with the TSDB store from that date onward, alongside the existing boltdb-shipper, so logs before the cutover stay queryable under the old store while new logs are indexed with TSDB.It's important to pick a future day for
LOKI_TSDB_FROM_DATE, e.g. the day after you first deploy this env: Both stores share the sameper-day table, so a past or same-day date makes them collide over that day's data and breaks querying it.
looks good! i haven't had time to properly test loki yet. are you running it? i had to do some changes for getting it to start but i couldn't commit them yet.
sorry, i meant to approve it