Bug:
I have Grafana/Loki running in a Pod with a control plane and two workers. I want the storage in Azure in a Store Account, but Loki isn’t able to write to containers.
Steps to reproduce the behavior:
I have Grafana/Loki running in a Pod with a control plane and two workers. I want the storage in Azure in a Store Account, but Loki isn’t able to write to containers.
All Pods are running
NAME READY STATUS RESTARTS AGE
loki-backend-0 2/2 Running 0 12m
loki-canary-hf2d8 1/1 Running 0 21m
loki-canary-v5m2p 1/1 Running 0 21m
loki-chunks-cache-0 2/2 Running 0 21m
loki-gateway-65fdf954d6-xrnsg 1/1 Running 0 12m
loki-read-7c4846964-n7pq5 1/1 Running 0 12m
loki-results-cache-0 2/2 Running 0 21m
loki-write-0 1/1 Running 0 12m
this is my Value.yaml for Loki
backend:
replicas: 1
deploymentMode: SimpleScalable
loki:
ingester:
chunk_encoding: snappy
querier:
max_concurrent: 4
commonConfig:
replication_factor: 1
schemaConfig:
configs:
- from: “2024-04-01”
index:
period: 24h
prefix: loki_index_
object_store: azure
schema: v13
store: tsdb
storage:
azure:
connectionString: “AccountName=XXXXXXX;AccountKey=XXXXXXX”
requestTimeout: 15
useFederatedToken: false
useManagedIdentity: false
bucketNames:
admin: “admin”
chunks: “chunks”
ruler: “ruler”
type: azure
tracing:
enabled: true
minio:
enabled: false
read:
replicas: 1
write:
replicas: 1
the documentation is not helping to much in helm/install-monolithic
The blobs are created in Azure Storage Account
and i am getting this error
level=error ts=2025-03-19T09:07:10.015321384Z caller=reporter.go:241 msg=“failed to delete corrupted cluster seed file, deleting it” err=“Delete “[https://storagedev1.blob.core.windows.net/chunks/loki_cluster_seed.json?timeout=1”:]context deadline exceeded”
and this
level=error ts=2025-03-19T10:51:50.697483083Z caller=flush.go:261 component=ingester loop=12 org_id=1 msg=“failed to flush” retries=3 err=“failed to flush chunks: store put chunk: write error: Put “https:// storagedev1.blob.core.windows.net/chunks/1/f4194a79703590ec/195adba6c9f-195adba6cf2-80adddef?blockidcomp=block&timeout=1”: context deadline exceeded, num_chunks: 1, labels: {filename=“C:\text.txt”, value_system=“system”, service_name=“TEST”}”
Expected behavior
I should connect with the connection string that I get from the Azure storage account and create the JSON in the directory and save the logs in the blob.
Environment:
- Infrastructure: Kubernetes, Storage Azure
- Deployment tool: helm