honeycomb-opentelemetry-go
self-hosted
honeycomb-opentelemetry-go | self-hosted | |
---|---|---|
1 | 29 | |
19 | 7,284 | |
- | 1.5% | |
7.4 | 9.1 | |
7 days ago | 7 days ago | |
Go | Shell | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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
self-hosted
-
Pydantic Logfire
I was responding to the One of the Sentry inconvenience is self-hosting: it relies on so many services it can be very complicated to maintain part, and also reminding readers that if they, too, hate companies that rug-pull their open source licenses, there is a band-aid for both parts
Compare https://github.com/getsentry/self-hosted/blob/9.1.2/docker-c... with https://github.com/getsentry/self-hosted/blob/24.4.2/docker-... for what life used to be like for running Sentry on-prem. It was awesome
It would take a ton of work to dig up the actual memory and CPU requirements of each one, but rest assured they're not zero, so every one of those services eats ram and requires TLC when, not if, they shit themselves. So, more parts == more headaches with all other things being equal
Then, I deeply appreciate that there are a whole spectrum of reactions to the various licensing schemes in use nowadays, and a bunch of folks don't care. I care, though, because I have gotten immense value from open source projects, and have contributed changes back to quite a few. It has been my life experience that any of those "source available" licenses usually are very hostile toward making local builds and if I can't build it to match how prod goes, then I can't test my fixes in my environment and then I can't contribute the PR with any faith
-
Sentry new TOS to use data to train AI with no opt-out
This is the point where I will point out that you can self-host Sentry free of charge :) https://develop.sentry.dev/self-hosted/
-
Low cost self-hosted bug reporting?
Sentry can be self hosted: https://develop.sentry.dev/self-hosted/
-
FSL: A License for the Bazaar, Not the Cathedral
The people we're concerned about are not the hundreds of thousands of Sentry users, including those that self-host.
We're concerned about people who have taken the software for the purposes of competing directly against us, that hinders our ability to monetize the work. Monetizing the work helps us continue improving the software and distribute it for free use, benefitting those aforementioned real users (e.g. https://github.com/getsentry/self-hosted).
-
Show HN: A open-source financial accounting alternative to QuickBooks
> I mean no slander or disrespect to anyone involved, but there was a DataDog alternative posted sometime in the last few weeks that had a docker-compose with like 15 containers in it.
Reminds me of Sentry: https://develop.sentry.dev/self-hosted/
This is their example docker-compose for self-hosting: https://github.com/getsentry/self-hosted/blob/master/docker-...
It has:
- exim4 (smtp)
-
OpenTelemetry in 2023
> What should people use?
I recall Apache Skywalking being pretty good, especially for smaller/medium scale projects: https://skywalking.apache.org/
The architecture is simple, the performance is adequate, it doesn't make you spend days configuring it and it even supports various different data stores: https://skywalking.apache.org/docs/main/v9.0.0/en/setup/back...
The problems with it are that it isn't super popular (although has agents for most popular stacks), the docs could be slightly better and I recall them also working on a new UI so there is a little bit of churn: https://skywalking.apache.org/downloads/
Still better versus some of the other options when you need something that just works instead of spending a lot of time configuring something (even when that something might be superior in regards to the features): https://github.com/getsentry/self-hosted/blob/master/docker-...
Sentry is just the first thing that comes to mind (OpenTelemetry also isn't simpler due to how much it tries to do), but compare its complexity to Skywalking: https://github.com/apache/skywalking/blob/master/docker/dock...
I wish there was more self-hosted software like that out there, enough to address certain concerns in a simple way on day 1 and leave branching out to more complex options like OpenTelemetry once you have a separate team for that and the cash is rolling in.
- Why use application stacks script installers
-
OpenObserve: Elasticsearch/Datadog alternative in Rust.. 140x lower storage cost
Sounds interesting!
Will you compare with qryn? Self-hosted sentry?
qryn.metrico.in/
https://develop.sentry.dev/self-hosted/
-
Insufficient logging
I haven't done it in years, but technically sentry is able to be self hosted https://github.com/getsentry/self-hosted
- Cloud Native Alternative to Sentry?
What are some alternatives?
jvm-serializers - Benchmark comparing serialization libraries on the JVM
Sentry - Developer-first error tracking and performance monitoring
opentelemetry-specificatio
Code-Server - VS Code in the browser
tel - OpenTelemetry API wrapper to make using opentelemetry-go more idiomatic
apprise - Apprise - Push Notifications that work with just about every platform!
go - The Go programming language
zammad-docker-compose - Zammad Docker images for docker-compose
blacklite - "Fast as internal ring buffer" Logback/Log4J2 appender using SQLite with zstandard dictionary compression and rollover.
ML-Workspace - 🛠All-in-one web-based IDE specialized for machine learning and data science.
SLF4J - Simple Logging Facade for Java
JupyterLab - JupyterLab computational environment.