Unable to See PurePaths

Hi Hariram,

Cross Profile PurePath's are not supported. The PurePath will only ever be seen in the Profile where it originates. Also the Services are not their "own" PurePath. The PurePath is the complete end-to-end transaction and the Services participate.

Why do you need two system profiles? Would your use case also work if you have one system profile with two agent groups? That would make both dashboards work on the same profile.

Thanks

Thanks Michael for the reply.

The problem is we are different teams. Services developer just want to see the services pure paths. In our scenario the purepath can traverse over more than 3 applications. we would like to have different profiles(different sensors, incidents etc) our applications, so they can be maintained easily.

Please let me know if there is a way to filter the pure paths by applications. 

Also, Please let me know how to filter  the  WebRequests Endpoints Dashboard by different applications.  

Thanks,.

Hi Hariram,

If the PurePaths are connected then it has to be the same system profile. While the separation of sensors works in the different profiles, the incidents and measures would only work in the originating profile. As I said cross-profile path are not supported.

For maintenance of sensors you can define different sensor groups for the 3 different agent groups. They can also be copy/pasted from and to sensor groups which allows the separate teams to work independently on them. You can use Business Transactions for separation of the Applications. Such a Business Transaction filter works in every dashlet including the WebRequests Dashlet.

You might want to upgrade to dt4. Most of your sensors will not be needed anymore due to AutoSensors, that will make maintenance a lot easier.

Thanks

Thanks Michael for the input. i will pass it to my team.