Skip to content

feat(storage): add fast open tracing attributes - #14877

Draft
Dhriti07 wants to merge 1 commit into
fast-open/07-public-apifrom
fast-open/08-tracing-attributes
Draft

Dhriti07 wants to merge 1 commit into
fast-open/07-public-apifrom
fast-open/08-tracing-attributes

Conversation

@Dhriti07

Copy link
Copy Markdown
Contributor

8/n of fast open BiDi reads.

With fast open, the blobReadSession span also covers reading the first range, and a readAs served from the fast open read takes ~0 ms with no request. Add span attributes so traces explain this:

  • gcs.bidi.fast_open (true/false) on the blobReadSession span: whether a read was sent with the open.
  • gcs.bidi.cache_status (HIT/MISS) on each readAs span of a session opened with fast open: HIT when the readAs was served from the fast open read, MISS when it sent a new read. Sessions without fast open don't get it.

@gemini-code-assist gemini-code-assist Bot 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.

Code Review

This pull request introduces OpenTelemetry tracing attributes to track the fast open configuration and cache status for Bidirectional Read (Bidi) sessions in Google Cloud Storage. Specifically, it adds the "gcs.bidi.fast_open" attribute to the "blobReadSession" span and the "gcs.bidi.cache_status" attribute (with values "HIT" or "MISS") to the "readAs" spans. Corresponding integration tests have been added to verify these tracing behaviors. I have no feedback to provide on these changes.

@Dhriti07
Dhriti07 force-pushed the fast-open/07-public-api branch from 7c4262e to 63fb3c4 Compare October 31, 2026 18:48
@Dhriti07
Dhriti07 force-pushed the fast-open/08-tracing-attributes branch from e740d72 to 540e2ca Compare October 31, 2026 18:48
Eighth step of fast open BiDi reads (go/fast-open-bidi-read, b/552263062).

With fast open, the blobReadSession span also covers reading the first range,
and a readAs served from the fast open read takes ~0 ms with no request. Add
span attributes so traces explain this:

- gcs.bidi.fast_open (true/false) on the blobReadSession span: whether a read
  was sent with the open.
- gcs.bidi.cache_status (HIT/MISS) on each readAs span of a session opened
  with fast open: HIT when the readAs was served from the fast open read, MISS
  when it sent a new read. Sessions without fast open don't get it.
@Dhriti07
Dhriti07 force-pushed the fast-open/07-public-api branch from 63fb3c4 to d14e2a9 Compare November 1, 2026 12:01
@Dhriti07
Dhriti07 force-pushed the fast-open/08-tracing-attributes branch from 540e2ca to 6bd1b9a Compare November 1, 2026 12:01

This branch has not been deployed

No deployments
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.

1 participant