I am facing a scenario where one of the processes jp*launcher.exe stopped monitoring and also not sending alerts. I see the following solution "Restart this process to gain full visibility into critical process- and service-level metrics". Any reason why this is happening? Attached the error snapshot.
Answer by Paul C. ·
Thanks @sebastian k. and @Ugochukwu N. Can you help me understand what is the purpose of the jp*launcher.exe process. It looks like it was added automatically as part of the Dynatrace agent setup on Windows platform. Will it affect any services if this is stopped running? is it mandatory to fix this error?
Answer by Sebastian K. ·
The question also is if somebody didn't disable full stack monitoring on this host (accidentally). After such operation, starting monitoring again may require restart. But you also should check agent logs on monitored host. There should be information what happened in time when monitoring was stoped.