In skywalking-java-agent, can I decide whether to report this Segment or not based on the state of the Segment?

[OrezzerO]

Currently, the sampling strategy of skywalking-java is that whether to sample has already been determined when creating the TracerContext. Is it considered to implement a layer of sampling before reporting to the server? In this way, it will be possible to decide whether to report according to the state of the Segment, such as the time consumption and whether an error has occurred or not.

Are there any implicit constraints that prevent us from doing so?

[wu-sheng]

What is the benefit of this? Collecting span and context propagation cost most CPU and memory, you chose to finish that but skip the report, why?

[wu-sheng]

They cut SkyWalking supported feature, it is their responsibility now.

[OrezzerO]

I can understand you, but it's uncertain to push the cloud service provider to make changes. I'd like to modify SkyWalking-Java on my own. What I want to ask the community for help is that I want to know if there are any unfeasible aspects in this matter, or get some suggestions so that I can solve this problem in a better way.

[wu-sheng]

What is the benefit of this? Collecting span and context propagation cost most CPU and memory, you chose to finish that but skip the report, why?

This is what I mean. I can't see the value to do that.
I can't tell why cloud vendor doesn't support that, most likely it is from billing plan perspective(charged by store cost, rather than received data)

[wu-sheng]

that I want to know if there are any unfeasible aspects in this matter

From upstream perspective, it is a low value and high cost sampling mechanism. It should not be done.

[OrezzerO]

Got it. Thank you for your reply.