I am not sure exactly what you mean.
If you mean to track software programs (batch jobs, etc.) that are affecting applications, Discovery wouldn't always know about that.
Discovery does find services and processes that are running at the time of discovery (only if they are running at the time of discovery).
So, probably some of those services and/or processes represent the applications you want to track.
But, Discovery wouldn't know which ones are interesting, of course.
You could write a pattern to trigger on those interesting services / processes and do something with the information. I'm not sure what.
But, also realize that you will surely miss some of the software programs you want to track.
Suppose someone runs a software program in the form of a batch job at midnight and the batch job affects an application somehow.
The job runs for one hour.
Now, suppose that we discover the hosts associated with the application at 8am.
We won't see the running process from that batch job, because the process went away at 1am.
I will enrich the idea with customer and make a decision to which way I will follow with him.
Thank you very much for this fast (very fast) response!!!
Later I will close (set correct) this post. Cheers and have a good day (or night)!
isn't this more of a TrueSight thing?