Hi all,
I need to define custom exit points for a datapower extension in order to have fully correllated snapshots but cannot find any decent documentation on this. All I can find is this:
"Please use the attached custom-activity-correlation.xml to define the exit point. Please contact help@appdynamics.com for any questions."
Are there any "how-to" documents on the creation of this xml file?
Thanks in advance,
-ed
I have reached out to Ed via helpdesk.
Thanks
Abey
Hi,
I am also looking for more detailed documentation about custom correlation xml; is there any or is this more per use case solved through support?
Thanks
Harald Rietman
Hi Herald,
Access other tickets which is not part of account that you have access is not an option unless we see your email id in such tickets, we request you to check if the below doc links provides some insights here:
https://docs.appdynamics.com/display/FEZ/Custom+Correlation
https://docs.appdynamics.com/display/FEZ/Custom+Correlation+Using+Validation
https://docs.appdynamics.com/display/FEZ/Common+Custom+Correlation+Scenarios
Regards,
Arun
Hi akumar,
I'd really like to have access to those documents you posted.
Could you please tell me, how I can access that documents? My AppDynamics account seems to be not valid to access the page behind the links.
Best regards,
Christoph Burmeister
Christopher,
Thanks you for inquiring. The articles you are requesting have recently been posted to our public Community Knowledge Base.
Custom-Correlation provides an overview and includes links to example KB topics. Note however, that custom correlation is a last resort in most cases.
You can review our documentation on auto-discovery of business transactions and other ways to instrument entry points and identify business transactions.
Organize Traffic as Business Transactions and related topics.
Hi Arun,
Thanks for the info. This info I already found and provides a high level description on the custom correlation. What I am interested in is detailed info on what can/should be inserted in the producer/consumer xml; for example how to add a key that is generated by the agent if the current code does not provide a way to uniquely identify a BT. E.g.
<producer enabled="true">
<instrumentation>
<class-name>com.customername.cpu.common.http2.apache.ApacheHttpClientImpl</class-name>
<method-name>execute</method-name>
<match-type>MATCHES_CLASS</match-type>
<param-types>org.apache.http.client.methods.HttpRequestBase,com.customername.cpu.common.http2.HttpRequest</param-types>
</instrumentation>
<identifiers>
<identifier name="HOST">
<data-gatherer-type>POSITION</data-gatherer-type>
<getter-chain>getUrl()</getter-chain>
<position>1</position>
<transformer-type>GETTER_METHODS</transformer-type>
</identifier>
</identifiers>
<correlation>
<payload-pointer>
<data-gatherer-type>POSITION</data-gatherer-type>
<getter-chain>this</getter-chain>
<position>0</position>
<transformer-type>GETTER_METHODS</transformer-type>
</payload-pointer>
<payload-operation>
<access-type>method</access-type>
<access-method>addHeader</access-method>
<param-types>java.lang.String,java.lang.String</param-types>
</payload-operation>
</correlation>
</producer>
How do I know what goes into the correlation section / payload-pointer? Or is this specific to the code that is being custom - correlated? Would access to the customer source code needed?
Thanks again
Harald
Hi Harald,
The config values and parameters will vary based on the code you are trying to instrument and the framework involved, Hope that clarifies your query.
Harald,
Yes, I think that you should seek direct AppD tech support. This is a subject that we've actually removed from our formal training offerings because it tends to be so case-specific that support is likely to be needed in most cases.
Good luck!
-Brad
Hi,
Thanks for the clarification.
Regards
Harald
Harold,
As a partner, I believe you have access to the Field Enablement Zone (FEZ) part of our community. Questions can be asked there as well as having access to additional technical information
Hello Ed,
Sorry to hear that you're having difficulties. Please email help@appdynamics.com and file a support ticket.
Thank you for joining the AppDynamics Community.