zeekayandHanzo Dev 1cb42b507b chore(components): drop redisreceiver — the last go-redis dependency ...

redisreceiver scrapes EXTERNAL Redis servers. We do not do that: this
distro exists for OUR telemetry only, and no config we ship or run
enables it.

Proof it is dead:
  - Live cluster (do-sfo3-hanzo-k8s, ns hanzo), all four otel ConfigMaps:
      otel-collector-config  receivers [zap, otlp]
      otel-agent-config      receivers [filelog]
      otel-logs-agent-config receivers [filelog]
      alertmanager-config    not a collector config
  - universe infra/k8s o11y/ + monitoring/: zero "redis" matches.
  - The staged langfuse fan-out overlay needs only basicauthextension,
    filterprocessor and otlphttpexporter — all retained.
  - In-repo, redisreceiver appeared only in go.mod, go.sum and the
    components.go import + factory registration. No test, no config,
    no doc referenced it.

Dependency that falls out:
  github.com/redis/go-redis/v9 v9.17.2 — `go mod why` showed it entered
  solely via components -> redisreceiver. It is now absent from the
  module graph entirely (`go list -m all` = 0 hits), so this repo no
  longer carries a foreign Redis client. Our KV client is
  github.com/hanzokv/go, which is what exporter/metadataexporter/cache
  already uses.

Remaining go.sum "redis" lines are cloud.google.com/go/redis, an
unrelated GCP API client pulled by the googlecloud receivers.

Verified: `CGO_ENABLED=0 GOWORK=off GOFLAGS=-mod=mod go build ./...`
exit 0 before and after; `go test ./components/... ./o11ycol/...` ok;
cmd/o11yotelcollector links clean.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-26 10:33:38 -07:00

..

components.go

chore(components): drop redisreceiver — the last go-redis dependency

2026-07-26 10:33:38 -07:00