Grafana Loki
Log aggregation component for Foundation observability and debugging.
Component Category
Monitoring and debugging / logging
Component Description
Grafana Loki is a log aggregation system built to collect, store, and query logs efficiently at scale.
Why It Is Used
In BullSequana AI Foundation, Loki provides centralized logging for platform services, helping operators investigate incidents, correlate events, and debug runtime behavior.
Learn More
Deployment notes
Loki 3.6 deploys in distributed mode in the grafana-loki namespace at sync wave 11 in the common tier, after the Alloy agents and gateway at sync wave 10. The data replication factor is three, and the ingester runs three replicas to satisfy it. The distributor, querier, compactor, and index gateway run two replicas each by default. Log chunks are stored in the configured S3-compatible object-storage backend with 30-day retention. That backend can be the in-cluster Rook-Ceph RGW service or the site's external S3 service.
Tenant organizations
Loki runs with multi-tenancy on: every write and query names an organization. Each log stream is stored in the organization the Alloy gateway assigns: platform for infrastructure logs, the tenant's organization for tenant-attributed logs, or quarantine for missing or malformed tenant context. Infrastructure logs from the per-node Alloy agents always go to platform, whatever the log body says.
Each organization is limited to 32 MB/s of ingestion with a 64 MB burst ([limits] of the grafana-loki component), so one tenant's volume does not stop ingestion for the others.
Queries go through the telemetry query gateway, which sets the organization itself. The platform Grafana Loki data source uses its global routes, which read the organizations the telemetry authorizer permits for the caller, and each tenant Grafana Organization uses its tenant routes. With the authorizer turned off, Loki allows no cross-organization queries and the platform data source reads only platform. See Observability and audit.
Interacts With
Grafana, which uses Loki as the log data source.Grafana Alloy, which forwards Kubernetes logs and tenant-routed application logs into Loki.BSQAI API, whose telemetry authorizer decides which organizations a tenant or global query may read.Rook Ceph, whose RGW service retains Loki log chunks, or the site's external S3 service when one is configured.