You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar feature requirement.
Description
In some cases, we need to determine the tenant ID of the current request based on certain information (such as domain name) in Spring Gateway. Usually, we customize a filter to implement this logic. However, after obtaining this information in the filter, due to the framework of WebFlux, it is currently impossible to directly pass it to downstream nodes through the context of SkyWalking.
Therefore, relevant tool methods are needed to process the snapshot information stored in the ServerWebExchange, so that it can be automatically injected into the context of the subsequent link through the header information "sw8-correlation".
Hi, I knew what is the use case. What I don't follow up on is why the code changes are so huge. Many new things are added.
Here are two things at least should be done
We need a proposal to explain what exactly you changed.
We need a plugin test to verify this propagation of collaboration context is working. A -> Gateway -> B for example, you should build a collaboration context in A, and check that in B, also tag it in the test. Then the plugin test tool could verify it.
Search before asking
Description
In some cases, we need to determine the tenant ID of the current request based on certain information (such as domain name) in Spring Gateway. Usually, we customize a filter to implement this logic. However, after obtaining this information in the filter, due to the framework of WebFlux, it is currently impossible to directly pass it to downstream nodes through the context of SkyWalking.
Therefore, relevant tool methods are needed to process the snapshot information stored in the ServerWebExchange, so that it can be automatically injected into the context of the subsequent link through the header information "sw8-correlation".
Use case
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: