Even when it's working, a reverse DNS lookup today can't tell you what an IP was yesterday. Anybody with a stolen credit card can get an IP from Amazon, Google, Microsoft, or other companies, and it will be allocated to somebody else tomorrow. That makes it useless for forensic investigations, for example.
For HTTP(S) traffic, whether on 80/443 or arbitrary ports, URL Filtering tries to log the URL the client requested. For HTTPS in particular, you would need to have HTTPS inspection enabled, which requires distributing a private certificate authority to clients and adding it to their x509 anchors. This can provide solid information in the future, but can't be done retrospectively: if it wasn't enabled at the time, the firewall may not have been able to log the information you want.
For arbitrary protocols (e.g., SSH, which is very unlike HTTP), your best bet would be to force clients to use a particular DNS server, then log DNS requests and responses on that server. Again, good for the future, but can't be done retrospectively.