在AWS X射线上，停止在ECS上的Docker容器中运行的节点API上追踪特定路径
我在ECS上的Docker容器中有一个节点API。我正在使用X射线来追踪传入请求。
我想指示X射线不要在我的节点API上追踪特定的API端点。这可能吗？
API端点是：
/api/upload/directUploadConfirmation
我不希望通过X射线追踪的端点。
我尝试的
我试图通过X射线控制台创建一个采样规则。我想欺骗并查看此参数URL，每秒捕获0请求。但是该计划之所以失败，是因为它不接受0，数字必须大于或等于1。
I have a Node API running inside a docker container on ECS. I am using X-Ray to trace incoming requests.
I would like to instruct x-ray to not trace a particular API end-point on my Node API. Is this possible?
The API endpoint is:
/api/upload/directUploadConfirmation
I do not want that end-point traced via X-Ray.
What I have tried
I tried to create a sampling rule via the X-Ray console. I wanted to cheat and see for this paritular URL, capture 0 requests per second. But that plan failed because it doesn't accept 0, the number has to be greater than or equal to 1.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
编辑：从那以后，CloudWatch控制台团队在生产中修复了这一点。感谢您找到这个问题！
=============================================== ============= =
仅确认，您是否使用 x - node.js ray sdk？如果是的话，请随时在那里打开一个问题，以便熟悉SDK的人也可以帮助您回答您的问题！
否则，我能够使用0
Reservoir size和0固定价格创建一个采样规则。下面是一张图片，显示如何到达X射线控制台创建此版本。”选项“ rel =“ nofollow noreferrer”> AWS文档列出了几个可以使用，包括，包括
url path。此选项在APIGW中不可用，但应在您提到的EC中可用。在我的图像中，我正在使用它将输出请求过滤为url路径/foo/bar。您能确认在哪里看到它不接受0吗？基于此，我可以尝试复制您的设置，看看是否遇到了同样的问题。
谢谢！
EDIT: The CloudWatch console team has since fixed this in production. Thanks for finding this issue!
=============================================================
Just to confirm, are you using the X-Ray SDK for Node.JS? If you are, feel free to open an issue there so people familiar with the SDK can help answer your question too!
Otherwise, I was able to create a sampling rule with 0
Reservoir Sizeand 0Fixed Rate. Below is a picture showing how to get to the X-Ray console to create this.The AWS documentation lists several Sampling options that you can use including
URL Path. This option is not available in APIGW, but should be available in ECS which you mentioned you are using. In my image I am using that to filter output requests toURL Path/foo/bar.Can you please confirm where you saw it fail to accept 0? Based on that I can try to replicate your setup and see if I get the same issue.
Thanks!