Hello,
Is there a way to disable or change the google-cloud-ops-agent port 20202? I have a VM which is hosting Splunk and listening on port 20202. To monitor disks attached to the same VM the agent was installed but caused an issue when the server went down and Splunk refused to come up due to port conflict.
My Scenario -
1. I want to keep monitoring the attached volumes
2. Splunk should also be running (can't change the port of this)
Solved! Go to Solution.
Hello @sdubey , indeed Cloud Ops agent uses ports 20201 and 20202 for internal monitoring. Unfortunately, at this moment these ports cannot be changed. There is an open feature request for this functionality. I have added your input to the request to reflect that this functionality is required by customers.
Hello @sdubey , indeed Cloud Ops agent uses ports 20201 and 20202 for internal monitoring. Unfortunately, at this moment these ports cannot be changed. There is an open feature request for this functionality. I have added your input to the request to reflect that this functionality is required by customers.
Hello @TeflonJohn , I checked and found that the current answer is correct today. There is no option to reconfigure these ports that are used "locally" within the machine. In my understanding these ports can be restricted for ingress communication from external addresses.
Since this set of ports is not configurable there is no option to add ports. You can describe your use case and contribute to the existing issue opened on Github.
Best regards,
Leonid