Skip to content

Demote tier2 refusal + ResourceExhausted logs to cut Cloud Logging volume - #962

Merged
maoueh merged 1 commit into
developfrom
feature/noble-peak-jay
Sep 29, 2026
Merged

maoueh merged 1 commit into
developfrom
feature/noble-peak-jay

Conversation

@maoueh

@maoueh maoueh commented Sep 29, 2026

Copy link
Copy Markdown
Contributor
  • "refusing Substreams ProcessRange request" was the single largest Cloud Logging contributor on substreams-workers (~20% of sampled bytes), logged at Info on every backpressure refusal.
  • Demoted its 4 call sites in service/tier2.go to Debug. Refusal rate/reason is already tracked by the existing substreams_tier2_rejected_request_counter Prometheus metric, so no operational signal is lost.
  • Left "incoming ProcessRange request" and "substreams request stats" untouched (the latter feeds a BigQuery sink, has a do-not-modify warning).
  • The paired "finished streaming call with code ResourceExhausted" gRPC completion log (~17% of bytes) came from dgrpc, not this repo. Spawned a linked session against dgrpc which added server.WithCodeLevelFunc (merged, Let callers override gRPC-code-to-zap-level mapping dgrpc#38); bumped the dependency here and wired tier2's gRPC server to demote ResourceExhausted to Debug while keeping the rest of dgrpc's default code-to-level mapping.
  • 4 other lifecycle log lines from dmetering that also showed up in the sample were already demoted to Debug by a prior commit already on this branch (d56dc47d); the Sept 27 sample likely predates that fix reaching production.

Cuts Cloud Logging volume on substreams-workers: these two log lines
accounted for ~37% of sampled bytes on every backpressure refusal.
Refusal rate/reason stays visible via substreams_tier2_rejected_request_counter.

Bumps dgrpc to pick up server.WithCodeLevelFunc (streamingfast/dgrpc#38)
and uses it to demote ResourceExhausted on tier2's gRPC server while
keeping its default code-to-level mapping for every other code.
@dfuse-bot

Copy link
Copy Markdown

🔍 Vulnerabilities of ghcr.io/streamingfast/substreams:b5b1eff

📦 Image Reference ghcr.io/streamingfast/substreams:b5b1eff
digestsha256:b6d79573db407e09f6cdd6599870616935bd9bc18315b459ca579b4d900dc2fd
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size125 MB
packages380
📦 Base Image ubuntu:24.04
also known as
  • noble
  • noble-20260911
digestsha256:496754492fb28b4d3049432f2ca787449331e23fb14f0dd3fffea86bf5a93eb4
vulnerabilitiescritical: 0 high: 0 medium: 10 low: 2

@sduchesneau sduchesneau left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM no problem, we have counters for debugging, and the tier1's point of view too.

@maoueh
maoueh merged commit 8a7a01f into develop Sep 29, 2026
12 of 13 checks passed
@maoueh
maoueh deleted the feature/noble-peak-jay branch September 29, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants