mirror of
https://github.com/nsnail/Ocelot.git
synced 2025-04-20 08:02:50 +08:00
3ac9b3bd87
* hacked together load balancing reroutes in fileconfig * some renaming and refactoring * more renames * hacked away the old config json * test for issue 213 * renamed key * dont share ports * oops * updated docs * mvoed docs around * port being used
61 lines
3.5 KiB
ReStructuredText
61 lines
3.5 KiB
ReStructuredText
Request Id / Correlation Id
|
|
===========================
|
|
|
|
Ocelot supports a client sending a request id in the form of a header. If set Ocelot will
|
|
use the requestid for logging as soon as it becomes available in the middleware pipeline.
|
|
Ocelot will also forward the request id with the specified header to the downstream service.
|
|
|
|
You can still get the asp.net core request id in the logs if you set
|
|
IncludeScopes true in your logging config.
|
|
|
|
In order to use the reques tid feature you have two options.
|
|
|
|
*Global*
|
|
|
|
In your configuration.json set the following in the GlobalConfiguration section. This will be used for all requests into Ocelot.
|
|
|
|
.. code-block:: json
|
|
|
|
"GlobalConfiguration": {
|
|
"RequestIdKey": "OcRequestId"
|
|
}
|
|
|
|
I reccomend using the GlobalConfiguration unless you really need it to be ReRoute specific.
|
|
|
|
*ReRoute*
|
|
|
|
If you want to override this for a specific ReRoute add the following to configuration.json for the specific ReRoute.
|
|
|
|
.. code-block:: json
|
|
|
|
"RequestIdKey": "OcRequestId"
|
|
|
|
Once Ocelot has identified the incoming requests matching ReRoute object it will set the request id based on the ReRoute configuration.
|
|
|
|
This can lead to a small gotcha. If you set a GlobalConfiguration it is possible to get one request id until the ReRoute is identified and then another after that because the request id key can change. This is by design and is the best solution I can think of at the moment. In this case the OcelotLogger will show the request id and previous request id in the logs.
|
|
|
|
Below is an example of the logging when set at Debug level for a normal request..
|
|
|
|
.. code-block:: bash
|
|
|
|
dbug: Ocelot.Errors.Middleware.ExceptionHandlerMiddleware[0]
|
|
requestId: asdf, previousRequestId: no previous request id, message: ocelot pipeline started,
|
|
dbug: Ocelot.DownstreamRouteFinder.Middleware.DownstreamRouteFinderMiddleware[0]
|
|
requestId: asdf, previousRequestId: no previous request id, message: upstream url path is {upstreamUrlPath},
|
|
dbug: Ocelot.DownstreamRouteFinder.Middleware.DownstreamRouteFinderMiddleware[0]
|
|
requestId: asdf, previousRequestId: no previous request id, message: downstream template is {downstreamRoute.Data.ReRoute.DownstreamPath},
|
|
dbug: Ocelot.RateLimit.Middleware.ClientRateLimitMiddleware[0]
|
|
requestId: asdf, previousRequestId: no previous request id, message: EndpointRateLimiting is not enabled for Ocelot.Values.PathTemplate,
|
|
dbug: Ocelot.Authorisation.Middleware.AuthorisationMiddleware[0]
|
|
requestId: 1234, previousRequestId: asdf, message: /posts/{postId} route does not require user to be authorised,
|
|
dbug: Ocelot.DownstreamUrlCreator.Middleware.DownstreamUrlCreatorMiddleware[0]
|
|
requestId: 1234, previousRequestId: asdf, message: downstream url is {downstreamUrl.Data.Value},
|
|
dbug: Ocelot.Request.Middleware.HttpRequestBuilderMiddleware[0]
|
|
requestId: 1234, previousRequestId: asdf, message: setting upstream request,
|
|
dbug: Ocelot.Requester.Middleware.HttpRequesterMiddleware[0]
|
|
requestId: 1234, previousRequestId: asdf, message: setting http response message,
|
|
dbug: Ocelot.Responder.Middleware.ResponderMiddleware[0]
|
|
requestId: 1234, previousRequestId: asdf, message: no pipeline errors, setting and returning completed response,
|
|
dbug: Ocelot.Errors.Middleware.ExceptionHandlerMiddleware[0]
|
|
requestId: 1234, previousRequestId: asdf, message: ocelot pipeline finished,
|