Allow pmm-admin to add external exporters with an IP address different of 127.0.0.1
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
Activity
Show:
Nurlan Moldomurov October 17, 2024 at 6:50 AM
Yeah, I checked code and you are right.
Pep Pla October 16, 2024 at 8:55 PM
External-serverless scrapes the data from the PMM server, which means that the client needs to open the firewall ports.
The problem is that sometimes a service can listen on one of the IP addresses but not on 127.0.0.1. We just need to be able to add the external service with a different IP address.
Actually, this can be changed manually in the vmagent configuration but only once you get the external exported running.
Nurlan Moldomurov October 9, 2024 at 9:07 AM
Hi, pmm-admin add external-serverless was done exactly for this reason.
Aaditya Dubey October 7, 2024 at 9:55 AM
Hi
Thank you for the report and feedback.
Currently, pmm-admin only allows external exporters that use the loopback address. If an exported listens in a different local address, you must manually change the agent's configuration.
If several instances of the same service are running on a server, you must change the port or use specific IP addresses for each service. The second option is not supported by pmm-admin.
I think we need to add an option like --host (similar to the one that already exists in external-serverless)