How do out of the box APIs defined in Dynatrace
Hi,
is there any article around how do out of the box APIs defined in Dynatrace.
Thanks for your help.
Also we have a sensor defined with the below classes
org.apache.catalina.connector.RequestFacade and org.apache.catalina.connector.Request these are part of one user defined sensor group. But when i look at the API it is part of "Servlet". So i am wondering how the API is defined and also if i took out this custom sensor, will this be shown in the purepath incase of real issue with that API? meaning is it auto detected when needed?
Hi,
The API definition is separate from the sensor rules. It is based on internal rules (for which I don't know any documentation - but maybe someone else reading here can provide details?) and user defined rules. In the API section of the system profile you can define the API for packages, e.g. com.compuware.apm.dynatrace should show as API 'dynaTrace'. Check out those entries in the documentation - https://apmcommunity.compuware.com/community/display/DOCDT50/System+Profile+-+APIs and https://apmcommunity.compuware.com/community/display/DOCDT50/APIs.
Regarding the auto sensors - you are correct, even if you do not place a custom sensor on this method it will show in the PurePath once it takes a significant amount of time. The auto sensor will take care of that.
Best, Roman
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 