I think it would be a good idea to implement an additional constructor on ObservationProxyExecutionListener which directly takes the host and the port instead of the whole R2DBC url.
In my usecase, I have access to the ConnectionFactoryOptions, which allows me to easily get the host and the port, but not the R2DBC url. To workaround this missing constructor, i would have to construct the URL just that the ObservationProxyExecutionListener then parses it again into host and port.
Hello!
I think it would be a good idea to implement an additional constructor on
ObservationProxyExecutionListenerwhich directly takes the host and the port instead of the whole R2DBC url.In my usecase, I have access to the
ConnectionFactoryOptions, which allows me to easily get the host and the port, but not the R2DBC url. To workaround this missing constructor, i would have to construct the URL just that theObservationProxyExecutionListenerthen parses it again into host and port.