- honeycomb-opentelemetry-go VS jvm-serializers
- honeycomb-opentelemetry-go VS opentelemetry-specificatio
- honeycomb-opentelemetry-go VS self-hosted
- honeycomb-opentelemetry-go VS tel
- honeycomb-opentelemetry-go VS go
- honeycomb-opentelemetry-go VS blacklite
- honeycomb-opentelemetry-go VS SLF4J
- honeycomb-opentelemetry-go VS opentelemetry-go-contrib
Honeycomb-opentelemetry-go Alternatives
Similar projects and alternatives to honeycomb-opentelemetry-go
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
self-hosted
Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
blacklite
"Fast as internal ring buffer" Logback/Log4J2 appender using SQLite with zstandard dictionary compression and rollover.
honeycomb-opentelemetry-go reviews and mentions
-
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
Stats
honeycombio/honeycomb-opentelemetry-go is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of honeycomb-opentelemetry-go is Go.
Popular Comparisons
Sponsored