<?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: HTTP parameters from an exit call in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730906#M7334</link>
    <description>&lt;P&gt;This is an class&amp;amp;method execution that always implies an HTTP exit call to another service in another application.&lt;/P&gt;
&lt;P&gt;So this is the process:&lt;/P&gt;

&lt;P&gt;Class.-&amp;nbsp;classname&lt;/P&gt;
&lt;P&gt;Method.- methodname&lt;/P&gt;

&lt;P&gt;And that execution generates a call to another application:&lt;/P&gt;
&lt;P&gt;Exit Calls:&amp;nbsp;HTTP&lt;/P&gt;
&lt;P&gt;&lt;A href="https://orinocoes-https-prod1.de.db.com:50138/GetDocument?documentId=10071640&amp;amp;authorizationId=000000000005141187-1511455831961&amp;amp;type=work" target="_blank" rel="nofollow noopener noreferrer"&gt;https://external-server:port/GetDocument?&lt;STRONG&gt;documentId&lt;/STRONG&gt;=10071640&amp;amp;&lt;STRONG&gt;authorizationId&lt;/STRONG&gt;=000000000005141187-1511455831961&amp;amp;&lt;STRONG&gt;type&lt;/STRONG&gt;=work&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Could it be possible to identify and split those 3 parameters and display them as Data Collectors information?&lt;/P&gt;
&lt;P&gt;Then we would be able to filter by each of them.&lt;/P&gt;
&lt;P&gt;Because those parameters are not being captures using the All (*)&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 23 Nov 2017 17:03:40 GMT</pubDate>
    <dc:creator>Maria_Garcia</dc:creator>
    <dc:date>2017-11-23T17:03:40Z</dc:date>
    <item>
      <title>HTTP parameters from an exit call</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730903#M7331</link>
      <description>&lt;P&gt;Hi team&lt;/P&gt;
&lt;P&gt;We have detecting some HTTP exit calls under Data Collectors, with name, for example "Exit HTTP1" and value:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://orinocoes-https-uat1.de.db.com:60345/GetDocument?documentId=59838&amp;amp;authorizationId=000000000000007372-1504688787562&amp;amp;type=work" target="_blank" rel="nofollow noopener noreferrer"&gt;https://server:port/&lt;STRONG&gt;GetDocument&lt;/STRONG&gt;?documentId=59838&amp;amp;authorizationId=000000000000007372-1504688787562&amp;amp;type=work&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;We would need to capture those HTTP parameters, but separately (&lt;A href="https://orinocoes-https-uat1.de.db.com:60345/GetDocument?documentId=59838&amp;amp;authorizationId=000000000000007372-1504688787562&amp;amp;type=work" target="_blank" rel="nofollow noopener noreferrer"&gt;documentId, authorizationId, type&lt;/A&gt;) to be able to filter by them on transaction sanpshots list.&lt;/P&gt;
&lt;P&gt;How to proceed to capture those parameters, included on an HTTP exit call?&lt;/P&gt;
&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 12:08:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730903#M7331</guid>
      <dc:creator>Maria_Garcia</dc:creator>
      <dc:date>2017-11-20T12:08:49Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP parameters from an exit call</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730904#M7332</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;

&lt;P&gt;If we use the Http data collector All (*), the Appdynamics should be able to capture all the parameters (GET/POST) in transaction snapshots-&amp;gt;call graph-&amp;gt;http params section as shown in the screenshot. If you are not able to see the same please send us the complete agent logs from the location &amp;lt;agent-install-directory&amp;gt;/logs to further debug the issue.&lt;/P&gt;
&lt;P&gt;Please refer to the attached screenshot.&lt;/P&gt;


&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Atyuha&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 16:17:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730904#M7332</guid>
      <dc:creator>Atyuha_Pal</dc:creator>
      <dc:date>2017-11-20T16:17:14Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP parameters from an exit call</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730905#M7333</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;SPAN&gt;Atyuha,&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN&gt;We have already configured&amp;nbsp; an HTTP paramter with name "All" and with value "*" (please check attached image).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;However the data collector always displays the HTTP exit calls as an "ExIt HTTP data collector, including as value the complete URL&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;And this is being classified under Business Data type (please find attached an example)&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 20 Nov 2017 16:56:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730905#M7333</guid>
      <dc:creator>Maria_Garcia</dc:creator>
      <dc:date>2017-11-20T16:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: HTTP parameters from an exit call</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730906#M7334</link>
      <description>&lt;P&gt;This is an class&amp;amp;method execution that always implies an HTTP exit call to another service in another application.&lt;/P&gt;
&lt;P&gt;So this is the process:&lt;/P&gt;

&lt;P&gt;Class.-&amp;nbsp;classname&lt;/P&gt;
&lt;P&gt;Method.- methodname&lt;/P&gt;

&lt;P&gt;And that execution generates a call to another application:&lt;/P&gt;
&lt;P&gt;Exit Calls:&amp;nbsp;HTTP&lt;/P&gt;
&lt;P&gt;&lt;A href="https://orinocoes-https-prod1.de.db.com:50138/GetDocument?documentId=10071640&amp;amp;authorizationId=000000000005141187-1511455831961&amp;amp;type=work" target="_blank" rel="nofollow noopener noreferrer"&gt;https://external-server:port/GetDocument?&lt;STRONG&gt;documentId&lt;/STRONG&gt;=10071640&amp;amp;&lt;STRONG&gt;authorizationId&lt;/STRONG&gt;=000000000005141187-1511455831961&amp;amp;&lt;STRONG&gt;type&lt;/STRONG&gt;=work&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Could it be possible to identify and split those 3 parameters and display them as Data Collectors information?&lt;/P&gt;
&lt;P&gt;Then we would be able to filter by each of them.&lt;/P&gt;
&lt;P&gt;Because those parameters are not being captures using the All (*)&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 23 Nov 2017 17:03:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/HTTP-parameters-from-an-exit-call/m-p/730906#M7334</guid>
      <dc:creator>Maria_Garcia</dc:creator>
      <dc:date>2017-11-23T17:03:40Z</dc:date>
    </item>
  </channel>
</rss>

