Only root nodes appear in the request dashboard. Rest of the nodes only appear in a trace.If a method is not instrumented by any of the component instrumentors (http,servlet,ejb,jdbc etc), then it'll be instrumented by DefaultMethodInstrumentor (as it was happening in this case). Unless there is a single trace collected (and that too at FullLevel), the agent simply ignores any method instrumented by DefaultMethodInstrumentor. That is preventing any methods to show up in the request dashboard.
DefaultMethodInstrumented - not deemed as root node and so agent discards it.
If its instrumented by CustomComponentInstrumentor, it is now seen as a custom "component" and so is considered worthy to be a root node.
Instead, we can define meaningful Custom Components. Then these methods can be considered root requests. Setting FilteringDefault to true (in recording.config) will open the flood gates and you may go through the requests to filter off the interesting ones.
1) Define Custom Components
Example - TEST including "com.xyz.test" classes. Optionally you can divide it further into separate components like (com.xyz.test.rt.) (com.hai.hcn.prox.base.) (com.xyz.test.system.) etc.
"TEST": MethodList (
include "com.xyz.test.",
),
2) There is a bit of plugin re-order required.Modify config\agent\type\generic.config and replace the plugins list with the one attached.
3) You might want to clean up the existing JavaEERequest model on the FMS and start fresh.
4) Stop all services for standalone jvms
5) Run preinstrumentor to regenerate bootstrap jar
6) restart all services
There should be meaningful requests seen on the dashboard.
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center