The integration suite runs against grafana/loki:3.7.10 (the version of the Grow Codes stack
catalog) with the Grow Codes Loki configuration (TSDB schema v13, structured metadata on,
volume_enabled: true, 7-day reject_old_samples_max_age), a second instance with
auth_enabled: true for multi-tenancy, and a test-only nginx gateway for Basic/Bearer
authentication and fault injection. Other Loki 3.x versions that expose the same HTTP API are
expected to work; report problems as an issue. Hosted Loki (Grafana Cloud) uses the same paths
under its own base URL with Basic authentication.
Functions the service cannot serve in the Docker suite¶
Every public function is called against the real service in the Docker suite. These cases
cannot be produced by the container and are covered by unit tests in all five languages:
Case
Languages
Reason
push status 260 (ingestion administratively blocked)
all
needs blocked_ingestion limits with a runtime-config file; not part of the Grow config
push 500/503 "Ingester is shutting down" (WAL disk ≥ 90 % full)
all
depends on host disk usage; the fixture keeps /loki on a tmpfs
Loki's own 429 ingestion rate limit text
all
needs more than 16 MB/s of ingest; the gateway's 429 + Retry-After is tested instead
dropped_entries in tail frames
all
only sent when a tailer falls behind under load
multi-tenant queries a\|b returning data
all
multi_tenant_queries_enabled is off (Loki's default); the suite checks the failure (400 on push, 500 on query)
real Grafana Cloud Basic/Bearer semantics
all
no credentials in CI; the nginx gateway proves the headers
HTTPS, mutual TLS and proxies
all
plain HTTP fixture; the shared transport tests cover them
The API is the same in every language; only the conventions differ (naming, durations, async
model). Specific to this SDK:
Topic
Difference
keywords
Rust names where and matchwhere_ and match_ (label is the cross-language name)
exporter names
Go and Rust also keep their original names PushExporter / OTLPExporter (OtlpExporter); LokiLogExporter / LokiOtlpExporter are aliases
category tail
Go and Rust expose the category methods on client.LogQuery() / client.log_query() because the service Tail has a different signature; TypeScript and Java call it logQueryClient(), Python log_query()
since
Java labels / series / indexStats take a TimeRange or LabelsOptions; use TimeRange.last(d) / LabelsOptions.last(d) instead of a server-side since (Java queryRange has since)
matrix samples
TypeScript and Java call matrix points samples, the other languages values
per-log-client allowlist
TypeScript logClient({ allowedLabels }) can override the config allowlist for one log client; the other languages use the client's allowedLabels (Python LokiLogExporter(client, guard=…))
environment
Java cannot change the process environment, so loadEnv sets system properties instead and returns the names it set