[GitHub] [incubator-shenyu] qicz edited a comment on pull request #2027: [ISSUE #2025] feature plugin: add request id plugin.

[GitBox <gi...@apache.org>]

qicz edited a comment on pull request #2027:
URL: https://github.com/apache/incubator-shenyu/pull/2027#issuecomment-915659263


   > To be honest, I don't think we need to set up a plugin to do this function. This function can be used as a configuration item in the request plugin as a function supplement. Setting up a separate plugin for this small function is not a good start, which may lead to confusion and redundancy in subsequent plugin management.btw, I don't think the request id in single gateway layer has the value of backtracking and trace like the order id or traceId
   
   @tydhot the `request id` is a service for every request that has any selector and rule. but the `request` is for a request that has the selector and rule. As far as I know, maybe the `request id` works like `traceId`, because business users are not cared for `traceId`, except `request id`. every people know about what is a request call.
   
   from aws:
   ```
   public String requestId()
   Returns the AWS request ID contained in this response metadata object. AWS request IDs can be used in the event a service call isn't working as expected and you need to work with AWS support to debug an issue.
   Can be overriden by subclasses to provide service specific requestId
   
   Returns:
   The AWS request ID contained in this response metadata object.
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shenyu.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org