asafm commented on issue #20845: URL: https://github.com/apache/pulsar/issues/20845#issuecomment-1864221655
Thanks for your comments. Before I continue, I must note that the PIP has been approved I think in September concluding almost 1.5 years researching it, and also lots of efforts into improving OTel Java SDK to match the harsh memory allocation requirements (almost zero) of Pulsar codebase. The latter is still in progress. So I don't see the community reverting that decision unless something so big will disrupt that decision. I personally don't see Micrometer Observation being that. You are free to raise this in the DEV mailing list of Apache Pulsar of course. >With [Micrometer Observation](https://micrometer.io/docs/observation) you can use 1 Java API to instrument for whatever observability pillars (metrics, traces etc.). With OTel you will need to use as many APIs as necessary to achieve the same goal. I don't see in that API how do I create an histogram or a counter. Can you explain? >It sounds a little bit like comparing incomparable libraries. You can’t compare a logging library to a metrics library. We were stating that we are like Slf4j but for observability. We never claimed that we will be Slf4j nor that we will reach their download statistics. I’m pretty sure that vast majority of applications are doing logging. Not all of the applications are gathering observability data. Slf4j made one API hence most adopted, for logging. It will be wonderful to have same for metrics, in the industry. IMO, Micrometer attempted to be that for metrics but didn't caught on, popularity wise. OTel tries that now, and as it still in early stages, the amount of companies involved, including outside Java ecosystem, IMO is a clear indicator it will be such. Only time will tell. >OTel was built with instrumentation scope in mind, which gives a sort of namespace per library or section of the code (Called Meter in the API). For Pulsar, it can be used to have one per plugin. Micrometer doesn’t have that notion. It’s great especially if Pulsar and another plugin are using same library (e.g. Caffeine for caching), thus in Prometheus or other libraries the metrics will override each other, but in OTel the meter provides an attribute for name and version, thus provide a namespace. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
