Open evg-tso opened 1 year ago
just wanted to mention that going with #2 doesn't preclude reusing it in java agent instrumentation, see azure-core
and couchbase-3.2
instrumenations for example
If you are in favor of this addition, I'd like to tackle it and work on a PR.
I'd appreciate your thoughts on the proper code location, either here or in folsom's repo.
I'd appreciate your thoughts on the proper code location, either here or in folsom's repo.
Looks like the folsom repo already contains several implementations for different metric libraries. WDYT about adding instrumentation there? You can tag me and Trask there, we'll help you review the OTel API usage patterns.
And after that gets merged, we can add a javaagent module that'll automatically apply the instrumentation.
Cool, I'll work on it
It seems abandoned, but I've implemented the support for OTel metrics in spotify/folsom
, the PR https://github.com/spotify/folsom/pull/229. Feedback appreciated.
@trask @mateuszrzeszutek
Thanks @korzepadawid ! I left a couple of comments in that PR.
Thank you @mateuszrzeszutek for the review. The PR with metrics is merged https://github.com/spotify/folsom/pull/229.
I've been thinking about tracing implementation, I might work on that in the future.
I've been thinking about tracing implementation, I might work on that in the future.
👍 Let us know if you open a new PR for that, we'll keep this issue open in the meantime.
Is your feature request related to a problem? Please describe. The spotify/folsom Memcached client supports custom metrics and tracing through interfaces.
I think adding support for OpenTelemetry for folsom can be rather easily created.
Describe the solution you'd like Folsom has built-in support for micrometer and opencensus, so adapting them to OpenTelemetry's spec should be rather simple.
Describe alternatives you've considered There are several options: