-
Notifications
You must be signed in to change notification settings - Fork 71
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
support to try to use request-id as trace-id when trace context absent #104
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a Lua expert just left a universal comment
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
segmentItems: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where could verify requestId
in this e2e test? I think I miss it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
covered.
skywalking-nginx-lua/test/e2e/user/config.yaml
Lines 23 to 29 in 19eaae6
- name: request_id | |
expected: /expected/requestId.yaml | |
entries: | |
- url: http://nginx:8080/info | |
method: POST | |
headers: | |
- Request-Id: skywalking-e2e-request-id |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean, we just would verify codes work, but can see whether request ID is used, right?
Could you check showcase, whether new tracer would have trace ID changing to request ID? |
No description provided.