<?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 Re: Instrument method level calls for .net in controller. in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Instrument-method-level-calls-for-net-in-controller/m-p/727251#M5680</link>
    <description>&lt;P&gt;Hi Yogesh&lt;/P&gt;

&lt;P&gt;If we understood correctly from the shared details. Under the same page url&amp;nbsp;"&lt;SPAN&gt;&lt;STRONG&gt;homepage.aspx&lt;/STRONG&gt;" you are making different&amp;nbsp;remote services Exit calls from different -2 methods inside the same class and you want to&amp;nbsp;collect the method level details on the controller UI.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Could you please verify while making&amp;nbsp;the Remote service Exit call, Are you passing any unique argument as a part of request like header, cookie&amp;nbsp;etc. If yes, you can use that while naming the BT. For example, screenshot attached for your reference.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;If it does not&amp;nbsp;help, you can create individual custom match rule POCO entry point on .Net class/ methods to detect the different BT and collect the BT level details. For reference please refer the following document&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO44/POCO+Entry+Points" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO44/POCO+Entry+Points&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Let us know if it helps or you have any question.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Ashish.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Mar 2018 08:00:23 GMT</pubDate>
    <dc:creator>Ashish_Singh</dc:creator>
    <dc:date>2018-03-12T08:00:23Z</dc:date>
    <item>
      <title>Instrument method level calls for .net in controller.</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Instrument-method-level-calls-for-net-in-controller/m-p/727250#M5679</link>
      <description>&lt;P&gt;I am facing issues while configuring .Net properties in controller. I have a scenario where the same url i.e homepage.aspx is appearing in transaction snapshot multiple times with different counts however many concurrent remote services are being called under the home.aspx page. I want to get method level details but i am unable to configure the same in on premise controller.Please provide the steps for the same at the earliest.&lt;/P&gt;</description>
      <pubDate>Sun, 11 Mar 2018 05:13:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Instrument-method-level-calls-for-net-in-controller/m-p/727250#M5679</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-03-11T05:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: Instrument method level calls for .net in controller.</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Instrument-method-level-calls-for-net-in-controller/m-p/727251#M5680</link>
      <description>&lt;P&gt;Hi Yogesh&lt;/P&gt;

&lt;P&gt;If we understood correctly from the shared details. Under the same page url&amp;nbsp;"&lt;SPAN&gt;&lt;STRONG&gt;homepage.aspx&lt;/STRONG&gt;" you are making different&amp;nbsp;remote services Exit calls from different -2 methods inside the same class and you want to&amp;nbsp;collect the method level details on the controller UI.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Could you please verify while making&amp;nbsp;the Remote service Exit call, Are you passing any unique argument as a part of request like header, cookie&amp;nbsp;etc. If yes, you can use that while naming the BT. For example, screenshot attached for your reference.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;If it does not&amp;nbsp;help, you can create individual custom match rule POCO entry point on .Net class/ methods to detect the different BT and collect the BT level details. For reference please refer the following document&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO44/POCO+Entry+Points" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO44/POCO+Entry+Points&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Let us know if it helps or you have any question.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Ashish.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Mar 2018 08:00:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Instrument-method-level-calls-for-net-in-controller/m-p/727251#M5680</guid>
      <dc:creator>Ashish_Singh</dc:creator>
      <dc:date>2018-03-12T08:00:23Z</dc:date>
    </item>
  </channel>
</rss>

