Since more & more buz apps are using TLS1.3 (Transport Layer Security), RUM should be able to monitor such apps well.
May I know why still BSM/APM 9.51 version is not supporting TLS 1.3 for https transaction?
As I see MF product every quarterly upgrading version of every product however compatibilities not checking by development team.
Till the time in next version you update TLS 1.3 version kindly suggest some alternate to https data without cipher key.
Thanks for submitting this idea. For RUM, to support applications that use TLS 1.3 somewhere in the chain of servers that receive user requests, we suggest deployment architectures that allow for RUM Sniffer’s Man-in-the-middle monitoring (for example, setup a monitoring segment without TLS 1.3 in the chain of servers) or use RUM CM Probe or use TCP level monitoring.
We plan to provide documentation with best practices to monitor applications that use TLS 1.2 with DH ciphers or TLS 1.3.
The technical reason RUM Sniffer would not decrypt TLS 1.3 traffic is because the protocol mandates DH ciphers. DH inherently blocks the Man-in-the-middle approach to monitoring employed by RUM Sniffer.