Ability to monitor the custom process and change the process name based on the different arguments

This feature request is to monitor the custom process end to end. Basically the running batch process on the server when we have requests to run different batch processes some on a particular schedule and some on an adhoc basis. So, when the batch is running its basically a JAVA process whose parent process is <java websphere dir>was-tools-unix/java/8.0/jre/bin/java that uses the websphere java. When we look into the instana console, it shows several processes with the same name of java, and its really impossible to open each process, go into the arguments and check which processs belongs to which environment and then which batch process name. Sometimes a single batch may have about 15-20 streamers running. Imagine in that case, there will be 20 such processes for each batch. Now if a single environment has some 4 batches to be run, in that case there will be 80 processes just for that one single environment (say TEST1). Now, what if TEST2 also has batches to run at the same time. There should be a way in the console where we could define some good naming convention based on the environment and batch name and not just display "<java websphere dir>/was-tools-unix/java/8.0/jre/bin/java"


And the second part is for the traces for these custom processes. As of now, when you select that custom process and look for its service in the console it shows nothing, no end points, no flow, no traffic, no transactions being executed or sql's being run. All these things provide a complete view of the entire transaction path, from the user interface to the backend system, including all dependencies and services involved. Traces help identify the root cause of issues, such as latency or errors, by providing visibility into the entire request flow.