Transaction splitting

[CommunityUser]

How works Transaction splitting in .net? Any documentation available?

I need a business transaction match rule in .NET where a value in a parameter dictionary, which maybe there, is filter?

Is it possible to check a private property change and split on the value the variable have?

[Alex_Fedotyev]

Transaction splitting is documented, just search for "Configure Transaction Detection" in the documentation.

We don't dupport splitting by a value in the dictionary right now, only the simple values of the properties or members.

So if you have a property that returns a proper value you can set up splitting.

[CommunityUser]

The documentation for .net is a bit to little for me,

maybe you can tell me what to configure.

I have now implemented a function

   void PrepareShellViewAppDynamics(string appdynamicsSplitter)

now I would like to use the content of the parameter appdynamicsSplitter to split the business detection

Maybe you can make a snapshot of the custom match rule tab transaction splitting

[Alex_Fedotyev]

There is one gotcha that you need to have that method as an entry-point, meaning you will have to start the business transaction with it.

In this case here is how it would look like - attaching couple screenshots.

[CommunityUser]

Hi

Due to a bug in your agent I had the problems and my trial and error did not work. I tested it with several Agents, from 3.6.0, 3.6.2.1040 and the 3.6.2.6040.

All have the same bug.

I did it like you proposed.

If I only have one rule (the spliiter rule), it works. It detects the call of the function. If there is a second rule it does not work.

I logged my calls to disk, so I could see it

But I am also interessed which calls go this way and which does not.

I tried two things

1. I have a splitter funtion which call the PrepareShellView or PrepareAppDynamicsShellView(string appdynamicsSplitter) depending if appdynamicsSplitter is empty. The Splitter Rule filter on the call of PrepareAppDynamicsShellView and the parameter (as you wrote). The second detecting rule looks for PrepareShellView without any thing else. If it is active:

The Agent put all calls to the second rule. I could verify it in the log file of the agent (BusinessTransactionsLog.txt)

The Splitter rule is never detected any more.

Next try

2. I made a rule which detect a later called function. (as I understood, the first detecting of a function counts)

Again all detected calls are summerized under the new rule. The snapshot starts with the the splitter call.

[Alex_Fedotyev]

I suggest filing a ticket for a support, so we could dig into the problem and resulution steps together.

[CommunityUser]

Suggest filing a ticket with Support so that they can guide you better on this.

Thanks