Open jasonprado opened 5 months ago
My input would be that this seems like a useful change that doesn't present any concerns I'm thinking of, as long as we aren't promising a particular log format long term (essentially making a soft API). Making it easier for a human to troubleshoot using logs seems very worthwhile.
Is your feature request related to a problem? Please describe. When examining DSS logs I would like to quickly filter requests from a specific authorized USS client.
Describe the solution you'd like Include the
sub
field of the request's decoded JWT in a field in the JSON log entry for each request.req_sub
would look parallel next toreq_dump
and similar fields.Describe alternatives you've considered
sub
value extracted.uss_base_url
from certain operations and filter based on them. Not all requests have this, however.Additional context I'd like to contribute this if we can get consensus on adding it and the format.