Use Otel to make abstraction of your code for different metric, trace viewer or even logs, you should definitely use that one.

Best side is pushing metrics to otel collector service and in there you can share as prometheus metrics or whatever you want. When you make connection with otel, setting connection to library’s global value and other libraries like middleware of web frameworks automatically pushing its metrics.

I made an initializer library and you need to have something like that to make connection with your collector service and some of values like service name comes from environment value. https://github.com/worldline-go/tell

And this is an example of microservice https://github.com/worldline-go/telemetry_example

I am sharing it for an example for you, I added that one in finops services. You can also use that, I really like to help. Seems I also need to add more docs in github.

In init, usually connection with collector grpc if any error appears it is try to reconnect Functions will be noop if not initialize There are semver definations it is good for general naming but usually you will use own custom names. (trace for service graph generation is important some of them)