AnsweredAssumed Answered

Backend Path

Question asked by Steve_Oak on Aug 24, 2016
Latest reply on Sep 11, 2016 by Hallett_German

Has anyone worked with Backend Path as discussed in the https://docops.ca.com/ca-apm/10-2/en/implementing-agents/java-agent/configure-java-monitoring/configure-backend-path-groups

 

We are having issues with a new application that is using REST WS calls and our member ID is embedded in the URI so we are getting massive Backend and WebServices metric trees and I have Case Comment 00456321 - REST API WebService Metric Explosion open with Support (which has them completely stumped at the time)...

 

One of the suggestions was to use the Backend Path even though it would only fit the Backend and not the WebService Client tree. I think I have built the statements as described but am not seeing any difference even in the Backend or Called Backend trees.

 

Given the following backend tree (only a snippet of the full tree):

 

WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/0E105E4541BA5426CCC598D493187E51/email|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/0E105E4541BA5426CCC598D493187E51/telephone|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/0E882CD089D8779F278666B90C5DAEDA/idcards/wellpointisg|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/1F74E9616D13F14E8A8223825CD897AF/address|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/1F74E9616D13F14E8A8223825CD897AF/benefits/1FZ5-20160101-20161231-MED/summary|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/1F74E9616D13F14E8A8223825CD897AF/claims|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/1F74E9616D13F14E8A8223825CD897AF/coverage-period|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/1F74E9616D13F14E8A8223825CD897AF/idcards|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/2B0F0E6242A41E44059B5D763025A14B/benefits/1G67-20150501-20151231-MED/servicelimits|GET:Average Response Time (ms)
WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/2B0F0E6242A41E44059B5D763025A14B/benefits/1G67-20150501-20151231-MED/summary|GET:Average Response Time (ms)

 

 

I have created a backend path statements:

 

ntroscope.agent.backendpathgroup.keys=members,default
introscope.agent.backendpathgroup.group.members.pathprefix=/v1/cp/members*
introscope.agent.backendpathgroup.group.members.format=members
introscope.agent.backendpathgroup.group.default.pathprefix=*
introscope.agent.backendpathgroup.group.default.format=Default

 

 

From this I would expect a Backend|member tree with the all the metrics accumulated in the normal 5 metrics types.

 

Also it says that you can use a wild card (*) but I was wondering if I can use multiple to pick up another groups for example with:

 

WebServices|Client|https_//uat.api.mycompany.com/v1/cp/members/2B0F0E6242A41E44059B5D763025A14B/benefits/1G67-20150501-20151231-MED/servicelimits|GET:Average Response Time (ms)

 

Can I put in a backend path:

 

introscope.agent.backendpathgroup.group.members.pathprefix=/v1/cp/members/*/benefits/*

introscope.agent.backendpathgroup.group.members.format=members-benefits

 

this would give me the best breakdown.

 

I have given up on Support coming up with something to limit the WebServices|Client trees until some future release but if I can at least get the Backend trees combined as above that will help our users to see what is happening but with the proliferation of metric trees they cannot really see since even metric groups won't work because of the number is separate trees.

Outcomes