[Chore]: Upgrade Loki 2.9.0 to 3.6.1 #98
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent Issue
Relates to #95
Summary
Upgrade Loki from 2.9.0 to 3.6.1. This is a major version upgrade requiring schema and storage configuration changes.
Key decision: Since this is a fresh logging stack (deployed Feb 2026) with no historical data worth preserving, perform a clean cutover to
tsdb+v13schema.Files to Modify
1.
docker-compose.yml(line 269)Update image version:
2.
config/loki/config.ymlFull configuration migration needed:
Current (v2.9.0):
index_, period:24hTarget (v3.6.1):
index_, period:24hallow_structured_metadata: false(not needed with v13)Key changes:
Breaking changes to handle:
service_namelabel auto-assigned on all ingested logs (review label limits)boltdb-shipperstorage directories from configAcceptance Criteria
/readyendpoint)Dependencies
egullickson referenced this issue2026-02-06 01:26:27 +00:00
Milestone: Loki 3.6.1 Upgrade Complete
Phase: Execution | Agent: Platform | Status: PASS
Changes Made
docker-compose.yml
grafana/loki:2.9.0->grafana/loki:3.6.1config/loki/config.yml
v11->v13boltdb-shipper->tsdbboltdb_shipperpaths withtsdb_shipper(new index/cache directories)shared_store: filesystemfrom bothstorage_configandcompactor(removed in Loki 3.0)allow_structured_metadata: false(not needed for current setup)720h)Breaking Changes Handled
shared_storeremoved (Loki 3.0 breaking change)service_namelabel auto-assigned on ingestion (no action needed)Commit
fc2dc21-chore: upgrade Loki 2.9.0 to 3.6.1 with tsdb/v13 schema (refs #98)Added to existing PR #102.
Verdict: PASS | Next: Production validation after merge