Showing results for 
Show  only  | Search instead for 
Did you mean: 

Oneagent custom method capture


Hi Team,

As in Appmon we have sensor placement feature which helps in

1) start a purepath with that method mentioned in sensor

2) capture the method in any relevant purepath where in the purepath tree method will be shown

So in Oneagent point 1 can be achieved by custom service detection and a new service will be created for that particular method but how to achieve point 2 in oneagent where I need to capture the method in a service which is already detected.




DynaMight Guru
DynaMight Guru

1) is correct, Custom service is the approach.
2) Still, Custom service is the approach to take also in the this case. A new service will be created and if you view PurePath from the already detected service, it will be shown as a called service.
Depending on your use case, method hotspot analysis might be also useful.

TEMPEST a.s., Slovakia, Dynatrace Master Partner

Hi Julius,

Is there any option to not make it as a separate service and show it in the existing purepath tree itself?

No, it will always be a separate service. This is a difference from Appmon behaviour.

What use case are you trying to solve?

TEMPEST a.s., Slovakia, Dynatrace Master Partner

There is a websocket communication happening in my application and I have created a custom service for the same. Though the front end response time is high I cannot see the same in dynatrace. Front end is having 4 seconds response but custom service shows response time in ms. So I guess there are more methods before or after which are not captured and need to capture the same.

And what is the response time at service which is the entry point?

TEMPEST a.s., Slovakia, Dynatrace Master Partner

There is only this one custom service as of now I have configured and this is showing response time in ms. Now am still asking the developer whether there is any other entry point except this because I cannot see where the response time is spent since browser shows 4 secs response time.