Please select the area the issue is related to
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/Configuration (Config files, settings, env vars, defaults)
Suggested Improvement
Problem
We need a way to track the log entires related to a specific request in the platform gateway logs. Previously we used the activity-id/correlation-id for this purpose.
Correlation ID should be picked up from the incoming request, using a pre-defined header name, if it exist or gateway should generate a new ID at the entry point if the request doesn't have the header.
This ID should be:
available in all the log entries related to a given request, including system logs.
the same ID should be passed to the backend systems as a header with pre-defined header name.
Related Issues
No response
Please select the area the issue is related to
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/Configuration (Config files, settings, env vars, defaults)
Suggested Improvement
Problem
We need a way to track the log entires related to a specific request in the platform gateway logs. Previously we used the activity-id/correlation-id for this purpose.
Correlation ID should be picked up from the incoming request, using a pre-defined header name, if it exist or gateway should generate a new ID at the entry point if the request doesn't have the header.
This ID should be:
available in all the log entries related to a given request, including system logs.
the same ID should be passed to the backend systems as a header with pre-defined header name.
Related Issues
No response