<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Nested method level instrumentation with Java Spring boot application in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Nested-method-level-instrumentation-with-Java-Spring-boot/m-p/737677#M10537</link>
    <description>&lt;P&gt;I am trying to get a nested method level instrumentation (like time spend in executing the method etc.) and i would like to specify the highest level method in the call stack. I would like to see the instrumentation data starting with the top most method covering all methods that come in the call stack.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is this possible to do with AppD?&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jan 2019 10:20:37 GMT</pubDate>
    <dc:creator>CommunityUser</dc:creator>
    <dc:date>2019-01-10T10:20:37Z</dc:date>
    <item>
      <title>Nested method level instrumentation with Java Spring boot application</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Nested-method-level-instrumentation-with-Java-Spring-boot/m-p/737677#M10537</link>
      <description>&lt;P&gt;I am trying to get a nested method level instrumentation (like time spend in executing the method etc.) and i would like to specify the highest level method in the call stack. I would like to see the instrumentation data starting with the top most method covering all methods that come in the call stack.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is this possible to do with AppD?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jan 2019 10:20:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Nested-method-level-instrumentation-with-Java-Spring-boot/m-p/737677#M10537</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2019-01-10T10:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: Nested method level instrumentation with Java Spring boot application</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Nested-method-level-instrumentation-with-Java-Spring-boot/m-p/737678#M10538</link>
      <description>&lt;P&gt;Anand,&lt;/P&gt;

&lt;P&gt;What you are describing is basically the intent of the call graphs within our &lt;A href="https://docs.appdynamics.com/display/PRO45/Transaction+Snapshots" target="_self" rel="nofollow noopener noreferrer"&gt;BT snapshot feature&lt;/A&gt;.&amp;nbsp; Have you looked into that?&lt;/P&gt;

&lt;P&gt;Warm regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jan 2019 12:18:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Nested-method-level-instrumentation-with-Java-Spring-boot/m-p/737678#M10538</guid>
      <dc:creator>Peter_Holditch</dc:creator>
      <dc:date>2019-01-10T12:18:16Z</dc:date>
    </item>
  </channel>
</rss>

