opentelemetry-go

This is all possible and quite neat to dive into the specifics, but if you really want to be able swap a std lib call, just turn it into a variable and change it. // code.go var now = time.Now // code_test.go func TestCode(t *testing.T) { nowSwap := now t.Cleanup (func() { now = nowSwap } now = func() time.Time { return time.Date(...) } } Examples Code: https://github.com/open-telemetry/opentelemetry-go/blob/main... Test: https://github.com/open-telemetry/opentelemetry-go/blob/490f...

Funny timing—I tried optimizing the Otel Go SDK a few weeks ago (https://github.com/open-telemetry/opentelemetry-go/issues/67...). I suspect you could make the tracing SDK 2x faster with some cleverness. The main tricks are: - Use a faster time.Now(). Go does a fair bit of work to convert to the Go epoch. - Use atomics instead of a mutex. I sent a PR, but the reviewer caught correctness issues. Atomics are subtle and tricky. - Directly marshal protos instead of reflection with a hand-rolled library or with https://github.com/VictoriaMetrics/easyproto. The gold standard is how TiDB implemented tracing (https://www.pingcap.com/blog/how-we-trace-a-kv-database-with...). Since Go purposefully (and reasonably) doesn't currently provide a comparable abstraction for thread-local storage, we can't implement similar tricks like special-casing when

Agreed. Some things they suggest aren't actually possible with their SDKs. For example, you cannot define a histogram's buckets near where you define the histogram. You have to give the global exporter (or w/e the type is) a list of "overrides" that map each histogram name => their buckets. This makes it extremely ugly when you have libraries that emit metrics. https://github.com/open-telemetry/opentelemetry-go/issues/38...

Try implementing an OTEL Tracer. This interface is insane, and should really just be a struct. https://github.com/open-telemetry/opentelemetry-go/blob/trac...

Yes, Application Observability is a lot of the purpose of this. Instrumentation will be richer, more accurate, low cost, and able to be of value throughout the application for the purposes of tracing and profiling. What it will mean is that thing like https://github.com/open-telemetry/opentelemetry-go will be able to use this to better instrument Go applications, and when OTel includes profiling (as well as traces) then you'll be able to use Pyroscope, Polar Signals, etc for that in addition to Tempo (or whatever you use for tracing), as well as using something like Grafana and Datadog to view all of the above. (I work for Grafana, but the above is relatively vendor neutral as yes we recently acquired Pyroscope and launched Grafana Cloud Profiles, and yes some of the people cited work for Grafana, but others are doing great work here too

(note: I'm not a maintainer in the Go SIG so I can't speak towards these issues with much authority) Definitely interested in how things can be improved here. What are you generally looking to accomplish? Hopefully it's just a matter of docs not accurately expressing what's possible today (a consistent theme for quite some time that's getting resolved, but it takes time). As for the dependency issues, is this something you'd have the time to file an issue about[0], or make an agenda item for the next Go SIG? At the end of each SIG there's also a moment where the SIG leader asks for stories about adoption (good or bad) and this would clearly count. I'd like to think that these issues are solvable, or at least solvable enough to make it worth it for you to adopt. [0]: https://github.com/open-telemetry/opentelemetry-go/issues?q=...

Please submit a bug at https://github.com/open-telemetry/opentelemetry-go/issues We want to make the SDKs rock-solid.

Disclaimer: I work on OpenTelemetry specification and Collector. I don't contribute to Go implementation but I encourage you to submit the feedback to https://github.com/open-telemetry/opentelemetry-go or https://gitter.im/open-telemetry/opentelemetry-go You can also attend Go SIG meetings and provide the feedback directly. SIG meetings are open for attendance: https://github.com/open-telemetry/community#special-interest... I am sure the Maintainers of Go implementation will appreciate your feedback.