As mentioned in here (https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/troubleshooting/tr...) and here (https://answers.dynatrace.com/spaces/482/dynatrace-open-qa/questions/190238/oneagent-vs-db2.html),
it is good to edit the watchdog port-range for the servers that are running DB2 to avoid port-conflict.
While this definitely is a concern if the OneAgent inside it is running as full-stack, I am wondering how about OneAgent in full-stack? do I still need to do it? Is this still a concern if OneAgent is running only in cloud-infra mode?
Solved! Go to Solution.
Just check if your DB2 listener is running on 50000 - that's just the default port, but I've seen in many environments listener configured on a different port. In that case you don't need to reconfigure the watchdog.