Ability to configure/change scraping port for eureka discovery targets

Had prometheus issue with following proposal:
" Sometimes metrics endpoint on target services registered in eureka are exposed on a specific non-business port, let’s say using “adminPort” metadata property.
Looking into eureka discovery plugin code, I can see that only Port, SecurePort properties are utilized from service eureka metadata.
It would be great to have that property configurable so end users can choose any numeric property as a target port for actual metrics scrapes."

and was redirected here by @roidelapluie

Please share a way to replace source Port with metadata_adminPort with relabeling (as advised in a ticket) so target scraping happens on adminPort.