not so simple as looks before:
as we don't have standard grpc and have micro, we need to implement reflection server by providing
https://github.com/grpc/grpc-go/blob/master/reflection/grpc_reflection_v1alpha/reflection.proto
and have only one rpc for it
rpc ServerReflectionInfo(stream ServerReflectionRequest) returns (stream ServerReflectionResponse);
}

if we fill response with valid data all stuff works fine with it

mostly we need to do copy/paste https://github.com/grpc/grpc-go/blob/master/reflection/serverreflection.go

Now that's interesting. I did not know that we could hack around the problem with this. An interesting solution. How much effort to do you think it is to add this by default to all services? We could add in server/grpc where we do extraction, have a reflection.go file for it?

I think that this is must be option to server. Because it adds additional handler to it. And also may be used to abuse it or something bad. Mostly we can add reflection.go file and slightly modify it for our use-case

So Reflection() option in grpc server package to enable it?

yes, probably

Consider adding an option for exposing grpc.Server, it will help us do more about things, such as registering prometheus, reflection, health etc..

we don't plan to leak abstraction and expose grpc.Server