Unknown Source Files for Captured Methods
I am trying to capture CreditCard authorization calls to an AS400 box(this is C based). I am unable to see these specific methods that deal with credit card authorization. This is a high priority issue in production, that is directly impacting the customer!The application that calls this AS400 is java based. The screenshot below is a sample of the methods I need instrumented. Does anyone know why the source file for these sensor would come back as unknown?and Line Number N/A?
According to one of the developers, the Oracle.e1.BSSV is a library. JC553BCC is a package. The classes and methods are inside the JC553BCC package.These files that contain the classes and methods are not the same file, but they are located in the same .jar file. 
Even after enabling capturing of setter and getter methods, with highest resolution for auto sensors enabled, I am unable to see that these methods are being called. They are located in the class browser, and are only present on a single JVM. Testing of these specific credit card transactions does execute through the correct JVM, and I can see all the other getter and setter methods related to the Credit Card Transaction. Please let me know how to instrument these methods.Thanks,Eric
Hi Eric...can you try attaching the images again (we are unable to see it)...
1st check point - go to agents overview, select the agent that corresponds to the app and under the details plane switch to deployed sensors, search for the custom method sensors you applied and verify that they show up (this is to make sure the method is instrumented)....
2nd check point - did you create a new sensor group for these custom method sensors? if yes then ensure that the sensor group is placed under the affected agent group.
These methods were placed last week and were visible under the deployed sensors tab. Today they are not coming up in the deployed sensors tab, I believe because there are no tests going through these specific transactions. I will ask to have them started, so that they will be visible in the deployed sensor tab. The sensor group is named after the agent group and is placed in the respective agent group as well. It is the first placed sensor group in the agent group(highest ranking priority for sensor placement).
Here are the pictures for what is described above:
In your test environment (non-prod), run a CPU sample (with highest sampling rate) on the affected agent for 2-3 mins at the same time have the developer execute credit card authorization transactions...check the sample to see if those methods show up.
All of the methods that I am trying to capture in the Purepath came up here in the CPU Sample. They are instrumented according to the popup window. However, these methods do not come up in the Methods dashlet, nor the PurePath dashlet.
Eric...there are 2 things you can try...1) lower the priority on the custom sensor group (put it below java web request), 2) IF option 1 doesnt give you the desired outcome, assuming the custom sensor pack has capture simply set to 'Active' change it to 'active and start purepath'...you can try one at a time...let us know if this works.
By starting the Purepath from that Set method, I am now seeing the method and the value of the integer I needed to see. It makes sense the original PurePath was not capturing this method because it executes in 0.01ms. I am thinking that the Setter and Getter methods must be captured on this agent group to pick up this one.
Lowering the priority of the custom sensor group did not work.
Thanks for the help. I'm gong to see if I can connect these single node purepaths to the original purepaths that were coming through.
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more! 
