topic Re: .net WCF POCO match rule - no transaction snapshot in AppD Archive

.net WCF POCO match rule - no transaction snapshot

CommunityUser — Thu, 23 Oct 2014 15:11:48 GMT

Hi,

I'm trying to set up AppDynamics to do a match rule for a business transaction.

I want to filter out all the calls to a WCF service method based on some parameter passed to the method.

I saw that for WCF only ServiceName and OperationName are available to configure as a match rule so I'm thinking of using .NET class method.

Attached is a screenshot of my configuration.

I can see that the new business transaction appeared in the list but there are no snapshots taken for it. There are pleanty of calls to that method done but none are displayed for my filter (restart application was done).

Also I want to extend it to split on parameter that is actually a property inside of my object that is passed as a parameter to the method.

Looking here https://docs.appdynamics.com/display/PRO14S/Getter+Chains+in+.NET+Configurations didn't help to much.

My method looks like this:

public class PaymentServicesBase
{...

public initiatePaymentResponse initiatePayment(initiatePaymentRequest request)

public partial class initiatePaymentRequest
{...
public int paymentMethodID;

paymentMethodID/2 for example being the parameter I want to split on.

Any help on this 2 matters will be great.

We have the Pro version of AppDynamics so maybe there are some hidden features I don't know about.

Thx very much,

Re: .net WCF POCO match rule - no transaction snapshot

CommunityUser — Thu, 23 Oct 2014 15:17:12 GMT

this is what I found in the Agent log file

2014-10-23 13:40:41.0663 3880 w3wp 2 11 Info BusinessTransactionRegistry Sending transactions to register [BusinessTransaction{id=0, name=, entryPointType=POCO, internalName=POCO InitiatePayment, componentId=231 ,applicationId=0, applicationComponentName=, matchCriteria=MatchCriteria{matchRule=CustomMatchPointDefinition{businessTransactionName='POCO InitiatePayment', matchPointRule=, entryPointType=, background=False, enabled=False, attachedEntity=, agentType=, matchRuleString=''}, namingConfig=}, createdOn=1/1/0001 12:00:00 AM, background=False, configuration=, createdNodeId=0, enabledForEUM=False, eumAutoEnablePossible=}, BusinessTransaction{id=0, name=, entryPointType=WCF, internalName=Capture All, componentId=231 ,applicationId=0, applicationComponentName=, matchCriteria=MatchCriteria{matchRule=CustomMatchPointDefinition{businessTransactionName='Capture All', matchPointRule=, entryPointType=, background=False, enabled=False, attachedEntity=, agentType=, matchRuleString=''}, namingConfig=}, createdOn=1/1/0001 12:00:00 AM, background=False, configuration=, createdNodeId=0, enabledForEUM=False, eumAutoEnablePossible=}]
2014-10-23 13:40:41.2691 3880 w3wp 2 11 Info BusinessTransactionRegistry overflow transaction: POCO InitiatePayment POCO

thx,

Re: .net WCF POCO match rule - no transaction snapshot

CommunityUser — Thu, 23 Oct 2014 17:05:04 GMT

Hello,

Thank you for joining the AppDynamics Community. Someone will assist you shortly.

Thanks,
Caitlin

Re: .net WCF POCO match rule - no transaction snapshot

Theo_Jungeblut — Thu, 23 Oct 2014 18:30:05 GMT

HI,

IT would be great if you could email me your complete and zipped %ProgramData%\AppDynamics\DotNetAgent directory.

Please do NOT attach it on the community post as it includes your credentials.

In case you are a Pro customer send it to help@appdynamics.com including the details in this post.

Otherwise, send it to tjungeblut @ appdynamic . com for review.

Thanks,

Theo