Since #16021, Spring Boot supports RSocket as a type of server applications (meaning there's a single RSocket server available and no HTTP server).
We should try and expose actuator endpoints in a meaningful way over RSocket.
I'm very interested in this as well. It will be interesting to see how this gets done as the routing in Framework is still basic (simple string). Spring Cloud Gateway needs similar functionality.
I think we might run out of time for this one. I'm going to move it to 2.x for now (@bclozel feel free to move back if you have something in hand already).
@bclozel I'd like to chat with you about it. Gateway needs something like this and I'd like to be not far off when I implement it there.
@bclozel I would love to help out on this one.
@snicoll and I are looking into this issue. We've discussed with the Framework team about this and it seems that:
We're pushing it back to 2.x as 2.3 will be based on Spring Framework 5.2 and we won't have time to cover all this in the next release.
Is this still open?
@AxelHeathnet yes
Any progress ?
@peter-natkaniec not yet - we suspect we'll need more infrastructure from Spring Framework itself, but we need to work on drafting this support first. We're looking at the number of votes on issues to prioritize work.
Looks like a big blocker for going into production without monitoring (I mean prometheus/grafana stack). Are there any other ways for monitoring r-socket based micro-services ?
Maybe https://github.com/micrometer-metrics/prometheus-rsocket-proxy ?