I have an executable that uses technology that is not deeply monitored (unsupported technology). This program can have hundreds of instances on each host, and would be differentiated by one of it's parameters.
I cannot figure out how to split this process by that parameter. The best I've seen is to use Declarative process grouping, but this requires a detection rule for each specific parameter that is possible. A few hundred in our case and difficult to keep updated. This results in an onerous amount of maintenance. It doesn't allow for naming/splitting process groups by any detected CLI args, only the explicitly configured name provided in the Dyntrace config UI.
I've tried to use `DT_NODE_ID` and `DT_CLUSTER_ID` without luck. I can successfully tag the process group with `DT_CUSTOM_PROP`, but this gets overwritten by whichever process started last and does not help with splitting. That is, it provides the tag, but that tag is later overwritten when another process joins the group. It does tell me that Dynatrace can see 👀 the environment variables, and it just doesn't care to use them for process grouping.
## Example
Processes:
* /path/to/exe -L program1
* /path/to/exe -L program2 -s 1234
* /path/to/exe -L program2 -s abcd
* /path/to/exe -L program3
Process Group Found:
* `/path/to/exe`- just the one is created
Process Groups Expected:
* `program1`
* `program2`
* `program3`
How does one automatically split this process group by either the command line parameters or environment variables, or any other option? Is splitting process groups limited to deep monitored processes only? Any help would be greatly appreciated as I feel like I'm going crazy here trying any and all config permutations.
