Skip to content

[XPTI] Add per-subscriber stream detail level control#21863

Open
againull wants to merge 1 commit intointel:syclfrom
againull:xpti_stream_detail_level
Open

[XPTI] Add per-subscriber stream detail level control#21863
againull wants to merge 1 commit intointel:syclfrom
againull:xpti_stream_detail_level

Conversation

@againull
Copy link
Copy Markdown
Contributor

Introduces a mechanism for subscribers to request different levels of optional data emission from producers on a per-stream basis, enabling fine-grained control over tracing overhead:

  • Added stream_detail_level_t enum (NONE, BASIC, NORMAL, VERBOSE)
  • Added optional xptiQuerySubscriberStreamDetailLevel subscriber callback
  • Added xptiGetEffectiveStreamDetailLevel producer API
  • Aggregation rule: effective level = max across all subscribers

Producers can use threshold checks to conditionally emit expensive optional data based on the effective detail level.

Also add XPTI_HAS_STREAM_DETAIL_LEVEL macro to enable compile-time feature detection for stream detail level functionality.

This approach allows to stay fully backward compatible: subscribers that define new xptiQuerySubscriberStreamDetailLevel callback can work with both old frameworks (that will ignore the callback) and new frameworks (that will recognize the callback).

Assisted-By: Claude Sonnet 4.5

Introduces a mechanism for subscribers to request different levels of
optional data emission from producers on a per-stream basis, enabling
fine-grained control over tracing overhead:

- Added stream_detail_level_t enum (NONE, BASIC, NORMAL, VERBOSE)
- Added optional xptiQuerySubscriberStreamDetailLevel subscriber callback
- Added xptiGetEffectiveStreamDetailLevel producer API
- Aggregation rule: effective level = max across all subscribers

Producers can use threshold checks to conditionally emit expensive optional
data based on the effective detail level.

Also add XPTI_HAS_STREAM_DETAIL_LEVEL macro to enable compile-time
feature detection for stream detail level functionality.

This approach allows to stay fully backward compatible: subscribers
that define new xptiQuerySubscriberStreamDetailLevel callback can work
with both old frameworks (that will ignore the callback) and new
frameworks (that will recognize the callback).

Assisted-By: Claude Sonnet 4.5
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