tel
honeycomb-opentelemetry-go
| tel | honeycomb-opentelemetry-go | |
|---|---|---|
| 1 | 1 | |
| 1 | 19 | |
| - | - | |
| 10.0 | 7.4 | |
| almost 2 years ago | 6 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tel
-
Go standard library: structured, leveled logging
I've played with trying to create an idiomatic wrapper for Go precisely because of this reason, but then didn't find time to continue with this.
https://github.com/henvic/tel
honeycomb-opentelemetry-go
-
Go standard library: structured, leveled logging
I see! Yeah, this is one where where otel-go is a lot harder to use, but it's something the SIG is looking at. A coworker of mine is helping drive a design that's sort of an "easy button" to configure all the things with the least-surprising defaults[0] and we're seeing how people like it in our SDK distribution that uses it[1]. I hope that sometime soon we'll have the design polished-up enough to get merged in. Like most OSS projects, it'll take some time but I'm confident we can get it done.
The main challenge is that there's a large variety of use cases to fulfill (e.g., someone wants custom context propagation, a custom span processor, and export over HTTP+json but not HTTP+protobuf) and today the answer to that is that you have to pull in all the libraries for all the things you need. It's a lot more energy you need to expend to get started with all of this than it needs to be.
As for logging support in the Go SDK, it's frozen mostly just due to lack of bandwidth and a need to finish what's already been started. Metrics have proven to be much more difficult and time-consuming to implement correctly across all languages, with Go being impacted harder than other languages (e.g., Python and .NET). I think you can expect logging integrations in the near-ish future though.
This is great feedback. I'll pass it on folks who haven't seen it. Thank you! And please feel free to file issues about all the things that rub you the wrong way
[0]: https://github.com/open-telemetry/opentelemetry-go-contrib/p...
[1]: https://github.com/honeycombio/honeycomb-opentelemetry-go
What are some alternatives?
opentelemetry-specificatio
jvm-serializers - Benchmark comparing serialization libraries on the JVM
self-hosted - Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
go - The Go programming language
blacklite - "Fast as internal ring buffer" Logback/Log4J2 appender using SQLite with zstandard dictionary compression and rollover.
SLF4J - Simple Logging Facade for Java
opentelemetry-go-contrib - Collection of extensions for OpenTelemetry-Go.