Hi Babar,
So if I understand this correctly, currently all WebSphere Process Groups and Processes are named like:
WebSphere AS CellXXXX ClusterXXXXXX (Node XXXX)
And this is too granular. You want them to have the simple name of:
WebSphere Server
Is this correct?
In that case you will have to create a Process Group Naming rule as follows:
This will have the following effect:
- You will have the same number of Process Groups, and the same number of Processes within these groups (process detection not affected)
- Every Process Group and Process will be named "Websphere Servers"
- Only where tecnology is detected as IBM WebSphere Application Server and there is a value for the property WebSphere server
If I misunderstood the requirements, please let me know.
Best regards,
Radu
Hey @Babar Q. this can be done quite easily. Go int your settings and select Processes and Containers > Process Group Naming and create a new rule.
If you put in: Websphere on {Host:DetectedName} then on each one the associated host name will appear in the name of the process! let me know if you need a hand!
@Babar Q. - I think what you need to do here is change the detection rules for these WebSphere Processes. Because of how entities work in Dynatrace, Process names are inherited from Process Group names. And because your Process Group is covering hosts PRO01, PRO02, PRO03, PRO04 - then when you say the name should be "WebSphere {hostname}" then all hosts within that process group are taken into the renaming.
With Process Group Detection rules you can actually tell Dynatrace how to create these process groups and have a more segmented grouping that limits the group to 1 per host. What you need to understand here though, you need to use a Process property that is unique across these servers.
Let's take an example:
The above process group detection rule will work on WebSphere processes, and every Process Group will be detected and named strictly by the WebSphere Server ID. So your Process Groups and Processes will become "WebSphere server01", "WebSphere server02", etc.
You will still have to create a process group naming rule as indicated by Chad if you want to pull in the hostname to have the naming like "WebSphere on PRO01".
However, if "WebSphere server01" is actually configured on more than one host (let's say we detect it on both hosts PRO01 and PRO02). Then the renaming will still have the effect of "WebSphere on PRO01, PRO02" because the process group has more than 1 member.
So when you create your process detection rule, you must make sure that whatever process property you are adding as the group identifier is unique across your hosts, otherwise you will always be in the same issue with the renaming.
Does this make sense?
@Ruben G. FYI I think you are having the same problem.
Hello @Radu S.
Do we need a restart after the process group detection rules creation to take effect?
I applied the below rule.
Regards,
Babar
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.
Featured Posts
