Relation between appmethod and app of Timeseries API for RUM and Service.

[suresh230591]

@Wolfgang B.

I made a call to
appmethod timeseriesId "com.dynatrace.builtin:appmethod.useractionduration" of RUM API. In the results it seems that appmehtod instances
are identified as APPLICATION_METHOD, app instances as APPLICATION.
None of the
entities (entityID)) returned in the appmethod call match an application object from /api/v1/entity/applications/(Application Topology API).

It seems appmethod belongs to different class. Is there any relation between appmethod and Application objects of Application Topology API.

Also the same thing apply for webcheck and servicemethod of Service.

[wolfgang_beer · Accepted solution]

The overall metric for an application is delivered by the 'app' timeseries, such as:

'com.dynatrace.builtin:app.apdex'. This timeseries deliveres the APDEX for a complete application, which has the same id as the application within Smartscape.

In case you subscribed a 'key user action' within an application, this is exported as an 'appmethod' (its a confusing naming here).

So 'appmethods' are the 'key user actions' that you subscribed within your applications.

[suresh230591]

Thanks Wolfgang,

That means appmethod is object of application class, If we want to see 'Key user action' for a specific application we need to filter with APPLICATION id.

[wolfgang_beer]

No that does not really work as all the 'Key user actions' are within a flat registry you can't filter for the application. Right now there is no way to check through the API which 'Key user action' is originating from which applications. That's something we have to consider as future enhancement.