12 Jun 2024 01:20 PM
We are observing duplicate MYSQL Process group instance creating for some time with Shutdown mode and then we are getting false alerts.
Is there specific reason to detect Duplicate process group instance for some time? And how to remove this?
12 Jun 2024 03:32 PM
Hi @VenkataSainath ,
First, please check if the duplicate process group instances have different PIDs (Process IDs). These might be different because the new instance is a different process following a restart or shutdown of the MySQL process.
When the first instance shuts down, Dynatrace detects it as unavailable and may create a problem if you have configured alerting for this process group.
To avoid false alerts, you can adjust your anomaly detection rules for this process group. This way, if you are certain that these process groups should operate with only one instance, you can prevent false alerting.
DEFAULT OPTION:
MY RECOMENDATION:
12 Jun 2024 03:48 PM
Hi @JoseRomero ,
Yes, I can do that But why other process got detected and it always in shutdown mode.
And the process uptime is more than 16days and not restarted also.
12 Jun 2024 06:14 PM
Hi @VenkataSainath ,
Can you check if you have deep monitoring for all of your process and no one of then are excluded of monitoring?
13 Jun 2024 10:41 AM
@JoseRomero , The Server has monitoring with Infra only monitoring mode
20 Jun 2024 10:32 PM
Hi Venkata,
I'm back from my vacation!
Hahaha
I recommend creating a case with Dynatrace One support if the platform is not working as expected.
21 Jun 2024 09:28 PM
@VenkataSainath most likely this is due to multiple processes running. It must not be a MySQL server process, but a other MySQL process falling into the same process group. Be sure to check metadata for each process in the process group and compare.
22 Jun 2024 03:24 AM
I think it’s related to host id if its windows server. You need to create host id using the oneagentctl commands
Regards
Esam