Conversation
| config { | ||
| network_mode = "host" | ||
| image = "grafana/loki:2.9.8" | ||
| image = "grafana/loki:2.9.17" |
There was a problem hiding this comment.
Production will run Loki 2.9.17 but local-dev uses 3.4.1 (docker-compose.yaml:29). This major version gap between environments may cause behavior differences and make it harder to catch production issues locally. Consider either upgrading production to 3.x or keeping local-dev on 2.9.x to maintain consistency.
matthewlouisbrockman
left a comment
There was a problem hiding this comment.
k, prepping for 3!
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
|
|
||
| loki: | ||
| image: grafana/loki:3.4.1 | ||
| image: grafana/loki:2.9.17 |
There was a problem hiding this comment.
OTLP endpoint unavailable after Loki version downgrade
Medium Severity
Downgrading Loki from 3.4.1 to 2.9.17 in local-dev breaks the OpenTelemetry integration. The native OTLP endpoint (/otlp) was introduced in Loki 3.0 and does not exist in 2.9.x. The otel-collector is configured to export logs to http://loki:3100/otlp, which will fail with 404 errors since that endpoint is unavailable in Loki 2.9.17.
There was a problem hiding this comment.
Good point. I'm going to revert the downgrade, as it's only temporary; loki 3 should come soon!
300f1a5 to
916efb1
Compare


Should be done before #1816 and #1815
Note
Low Risk
Simple image tag bump in deployment configs; main risk is Loki version incompatibility/regressions during rollout, with no code-path or data-model changes in this PR.
Overview
Upgrades Loki to
grafana/loki:2.9.17in both the GCP Nomad job (iac/provider-gcp/nomad/jobs/loki.hcl) and the local devdocker-compose.yaml, aligning environments on the same Loki release.Written by Cursor Bugbot for commit 300f1a5. This will update automatically on new commits. Configure here.