24 May 2023 08:29 AM - last edited on 13 Jun 2023 04:44 PM by Ana_Kuzmenchuk
Hi currently we have issue about the services got merged and want to find out why and split it.
We have our service on different cluster (we will call it cluster A and cluster B)
It used to detect the service as Service_A and Service_B. and We monitor it seperately.
After we redeploy oneagent it detect as same service. Service_A but run on both cluster A and B.
We expect the result to be detect as 2 services( Service_A runs on cluster A, Service_B runs on cluster B)
is there anyone had faced the same issue before??
24 May 2023 10:48 AM - edited 24 May 2023 10:42 PM
Hi @thitiphans
I had the opposite issue. Once after one agent update. Application clusters legs were restarted becasue of patch management in different time (24 hours later). My original merged services splitted to two different services. I did not know the reason why. So I had to use the service detection rules. I used it to merge them again, maybe you can use it to separate it based on hostnames, if you would like to analyse them separetly by cluster legs.
I hope it helps.
Best regards,
Mizső
24 May 2023 08:50 PM
@thitiphans conditions must have changed in your case. Any chance the process group merged into a single one in your case? Services from different process groups are always monitored separately, so I guess if the service properties are the same, your process group have merged.