The NAM documentation states:
There's a default list of RPC GUIDs which RPC decode reports by the readable service endpoint names. Other GUIDs can be added to the list via configuration means
Service endpoint names are recognized, but not the service transaction/operation call names, which typically are encrypted.
I could not find anything that says were this configuration is done. I have an old COM+ application that I would like to monitor with NAM. I have a trace file, I assume I only need the Endpoint (tcp/135) traffic to figure this out. Wireshark does not seem to decode this well but Message Amalyzer shows a lot of GUIDs.
There is a process controlling the mappings. It’s is described in documentation, see https://www.dynatrace.com/support/doc/nam/shortlink/id-service-module-and-task-assignments . It’s controlled from the Console and uses configuration files on the CAS and/or manual entries in the console screen.