Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
02-07-2020 01:45 PM
Given the program below that accepts arguments from the command-line via the string[] args parameter, how do I setup a business transaction that will split based on the first value, args[0]?
I have it set to use Parameter index 0 and a Getter chain value of .[0] right now, which doesn't seem to work. For the Getter chain I have also tried string/0 and int/0 an those do not seem to work either.
The Using Getter Chains documentation is not very clear about this and does not provide clear example of accessing a value in a parameter that is an array.
using System;
using System.Collections.Generic;
using System.Linq;
public class Program
{
public static void Main(string[] args)
{
switch(args[0])
{
case "A":
DoA();
break;
case "B":
DoB();
break;
}
}
private static void DoA(){}
private static void DoB(){}
}
Solved! Go to Solution.
02-08-2020 09:53 AM
Hi Andrew,
As the below share code is for the standalone application, where main method will only call one time. So, to detect the transactions for instrumented application below are min requirement-
Now, if we see the example. Parameters are passed on Main method, based on that your switch case will execute and required methods will execute.
So, we would suggest creating POCO BT on DoA and DoB methods individually.
Let us know if it does not help. In case you have any question, could you please share some more details of the requirement and on which kind of application and transaction type you are creating the BT.
Thanks,
Ashish.
02-10-2020 09:40 AM
That does answer my question. I had hoped to use the BT on the Main method as a fallback for unconfigured specific BTs for a .Net console application that acts as a job/process runner. It would be nice for this scenario to work, though as it would save a lot of time configuring BTs and allow instrumenting the entire process as there is a bunch of setup code that runs before each job/process that is not currently captured because we have to configure the BT for something farther down the call chain.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form