As seems to stem from the discussion in #4934, request logging implementation and configuration seem to have a couple of confusing features, which might be a bit misleading for the users.

I'll try to summarize some of my and @PhilipGough's observations below:

• There is no simple way to determine if the request logging for a component has taken effect - perhaps it would make sense to log a line with this information (e.g. "logging for XY has been enabled")
• A configuration to log requests for particular server (HTTP, gRPC) on a component requires to specify a port, but it is not clear which port the user should specify and why this is required. Perhaps specifying the port is not necessary?
• It is possible to configure a log level for the requests logs, but the logs still do not seem to appear until log.level=debug is used. I think normal user expectation would be to set the level and see the logs being logged at that level, without the need to set log.level=debug.
• URL path configuration seems to be working on the basis of exact match, per the comment in #4934 (comment), but this is insufficient if URL parameters are passed as well.