process-exporter
process-exporter copied to clipboard
Exporter's port not officially allocated conflicts with another exporter
Hi!
It seems that this exporter's port has not been allocated in the official prometheus port registry https://github.com/prometheus/prometheus/wiki/Default-port-allocations, and it conflicts (not sure if always or this is a recent thing), with the port from https://github.com/matsumana/td-agent_exporter. It would be nice if an official port allocation got requested.
Hi @guillemj,
Thanks for the suggestion. I'm reluctant to change the current port since that would likely break many user's setups. Not sure I see a good path forward here, do you?
Right, I've just checked the td-agent project and it seems it started using the port later than process-exporter (2017 vs 2016; or https://github.com/matsumana/td-agent_exporter/commit/000f10553a5eae985dfbfd0beb1450782c1b82b9#diff-f4d7b652a668444bc7ecd314adb7832856159d2f34869caac795b2c1c52acc54R21 vs 751459ad6079c7463d2ec67ae0290f3e15c17b6a).
Also it looks to me like the td-agent is fringy, certainly compared to the process-exporter. So I think a way forward would be to kindly ask the td-agent developers to use a different port, and at the same time perhaps add it to the port-allocation wiki, so that people are aware of the usage? I think you might be in a better position to do the above, but if you'd prefer I'd be fine requesting this to the td-agent developers.
Actually, I've just noticed that a few ports are already noted in the (publicly editable) wiki as used by multiple projects, so I've gone ahead and added it there. But I guess at least notifying the td-agent developers about the collisions would still be best.