loki icon indicating copy to clipboard operation
loki copied to clipboard

filesystem and bucket not working together

Open quiquos opened this issue 9 months ago • 0 comments

Describe the bug I have Loki 2.5.0 in kubernetes that is working perfectly with Filesystem. Now we need to implement a bucket and update the Loki version without losing the existing data in the FileSystem of version 2.5.0. When trying to use FileSystem and Bucket (tested with version 2.9.4 and 3.0), only the bucket is working, the file system does not appear.

To Reproduce Steps to reproduce the behavior:

  1. configure myvalues.yaml to use both schema configs (filesystem and bucket)
  2. Install LOKI with helm (version 2.9.4 or 3.0)
  3. use grafana to check data

Expected behavior View logs from both schemas

Environment:

  • Infrastructure: kubernetes
  • Deployment tool: helm

Screenshots, Promtail config, or terminal output myvalues.yaml

loki: auth_enabled: false ingester: lifecycler: ring: kvstore: store: inmemory replication_factor: 1 chunk_idle_period: 3m chunk_block_size: 262144 chunk_encoding: snappy chunk_retain_period: 1m max_transfer_retries: 0 wal: dir: /data/loki/wal

schemaConfig: configs: - from: 2024-04-17 store: boltdb-shipper object_store: aws schema: v12 index: prefix: index_ period: 24h - from: 2020-10-24 store: boltdb-shipper object_store: filesystem schema: v11 index: prefix: index_ period: 24h storage_config: aws: access_key_id: b3b5075... bucketnames: bucket-Loki-Dev endpoint: https://frdvdrigd38a.compat.objectstorage... s3forcepathstyle: true insecure: true region: eu-frankfurt secret_access_key: "8P9XJm... boltdb_shipper: shared_store: filesystem active_index_directory: /data/loki/boltdb-shipper-active cache_location: /data/loki/boltdb-shipper-cache cache_ttl: 8760h filesystem: directory: /data/loki/chunks

quiquos avatar May 20 '24 11:05 quiquos