Skip to content

matrix: add built-in span processor's decorator requirement #3189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

tsloughter
Copy link
Member

Changes

Updates spec-compliance-matrix.md for the requirement of being able to "decorate" the built-in Span Processors:

SDK MUST allow users to implement and configure custom processors and decorate built-in processors for advanced scenarios such as tagging or filtering.

@tsloughter tsloughter requested review from a team February 8, 2023 22:34
@@ -82,6 +82,7 @@ formats is required. Implementing more than one format is optional.
| [IdGenerators](specification/trace/sdk.md#id-generators) | | + | + | | + | + | + | + | + | + | | + |
| [SpanLimits](specification/trace/sdk.md#span-limits) | X | + | + | | + | + | + | + | | - | | + |
| [Built-in `SpanProcessor`s implement `ForceFlush` spec](specification/trace/sdk.md#forceflush-1) | | | + | | + | + | + | + | + | + | + | |
| [Built-in `SpanProcessor`s implement decorators](specification/trace/sdk.md#span-processor) | | | | | | | | | | | | |
Copy link
Member

Choose a reason for hiding this comment

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

I'm confused by what a decorator is. Seems like this needs to be clarified first before adding it to the matrix.

Copy link
Member

Choose a reason for hiding this comment

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

If I understood the conversation in slack correctly, this pull request is just a catalyst for exactly that

Copy link
Member Author

Choose a reason for hiding this comment

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

Right. I figure this will bring it to the attention of some who don't know about it already and then discussion can be had here and then in the SIG meeting on Tuesday. That should at least start the process of clarifying what they are so another PR can be made to improve the spec.

@github-actions
Copy link

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Feb 17, 2023
@dyladan
Copy link
Member

dyladan commented Feb 24, 2023

This does not seem to have had the intended effect

@tsloughter
Copy link
Member Author

Yea. There didn't seem to be appetite for actually having this be part of the spec, despite it already being part of the spec :). I was going to make an alternative PR to remove it entirely from the spec and see what happens with that, but I suspect the same result.

There will need to be a concerted effort to push forward a proposal to replace "decorators" I think.

I'd propose a WG to happen now but don't think the TC has the resources to sponsor another one at this time.

@github-actions github-actions bot removed the Stale label Feb 25, 2023
@github-actions
Copy link

github-actions bot commented Mar 5, 2023

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Mar 5, 2023
@github-actions
Copy link

Closed as inactive. Feel free to reopen if this PR is still being worked on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants