This page provide workarounds for some issues, when PurePaths is not displayed properly.
PurePath contains "Execution Path Not Instrumented" messages
There could be two possible reasons for that:
- No instrumented method on the RMI receiving end.
You must have at least one instrumented method as an entry point. You can achieve that by using custom Method Sensor Rules.
- Thread tagging sensor is not placed.
Some specific cases, for example JBOss, require thread tagging. The ground for that is the method invocation is received in one thread, but the handling is done in another thread. To follow PurePath properly you need to thread tagging even when methods on the receiving end are instrumented.