Hi all,
Please know that Process Group Detection Rules will require a restart. It is at process startup time that we detect all the properties and apply the new rules, so that’s why it is a requirement. Sorry, I should have specified this.
Hi all,
Please know that Process Group Detection Rules will require a restart. It is at process startup time that we detect all the properties and apply the new rules, so that’s why it is a requirement. Sorry, I should have specified this.
And also just to iron out some confusion here…
Custom detection rules
Are only required when Dyantrace does not detect your process at all. So basically you point it to the exact path where the .exe is located and you tell it “hey, this is a process. When you see it running, monitor it”.
Since @Babar Q. is already seeing Processes for WebSphere, there is no need to create any rule under this section.
You only need to work with Process Detection Rules (which assume that you already have visibility of your processes, but you just want to change how they’re grouped):
@Chad T. you are correct, this option does only work with “deeply monitored processes”. WebSphere is a deeply monitored process, it is based on the Java technology and it is a known framework around it so we monitor it via deep injection. This option will work with WebSpehere.
Dear @Radu S.
Thank you for the clarification. I will share the feedback. once done with the complete exercise.
Regards,
Babar