-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
help request: 插件 request-id 与 opentelemetry 结合 #7239
Comments
maybe we can raise the priority of |
SGTM |
我觉得 request-id 应该是级别最高的吧?无论请求是否成功响应,都应该记录一个 request-id 方便排查问题? |
LGTM. |
十分抱歉,我对 |
看了下2.11版本的插件优先级:
requests-id的执行阶段是比较靠前的,不过看最新的代码,opentelemetry 的优先级由-1200改为12009,排到了第二位: apisix/apisix/plugins/opentelemetry.lua Line 179 in 70ba952
apisix/apisix/plugins/request-id.lua Line 67 in 70ba952
所以@shuqingzai 你只需要改下插件代码里面的 priority 就能改变这个执行阶段顺序。 @spacewander 所以这里的改动很简单,不过问题是这个x-request-id应该排在第几位执行呢? |
Maybe after |
@tokers request-id现在的优先级不低(排在第四位),感觉这里的问题可能还是 opentelemetry 的优先级调得太高了,超过了request-id。 |
opentelemetry is moved to the top so we can report requests which are rejected. |
嗯嗯,那这个调整是在apisix这边改还是用户自己改 |
You can change it yourselves, and submit it to APISIX. |
Description
问题
request-id 支持三种方式生成: ["uuid", "snowflake", "nanoid"]
[0-9a-f]{32}
规范,request-id 并没有这样的生成器,是否可以新增一个 request-id 的生成方式?Environment
使用版本
官方
docker
镜像:apache/apisix:2.14.1-centos
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: