Top 23 tag-production Open-Source Projects
-
-
-
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.
-
self-hosted
Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
First, sign up for a free account at https://sentry.io. Create a new project and make note of your DSN (Data Source Name).
I hope this tone comes across correctly as just a suggestion: I get a lot of mileage out of the "Send Feedback" option in DDG, which they claim actual humans do read. It can help move bug reports out of these HN threads into a more context-aware flow, and also makes me feel like any bad outcome has the possibility of improving, unlike systems that don't provide a "I feel bad about this experience" button
If you were thus inclined, https://gitlab.com/glitchtip/glitchtip#glitchtip is the actual open source Sentry implementation which (as far as I know) would enable gluing https://docs.sentry.io/platforms/javascript/user-feedback/#u... to the search results (which itself is still MIT: https://github.com/getsentry/sentry-javascript/blob/7.102.1/... )
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
So cool to see the CTO of Sentry here! This makes some sense to me - I'm actually following an issue with Sentry I had recently and although it's not being fixed anytime soon at least I know the status.
https://github.com/getsentry/sentry-python/issues/370
I'd love to believe that one day someone will crack the nut of "Sentry puts a bounty on this issue and YPCrumble decides to make a PR because it's something he's experiencing AND he'd get some experience working on the Sentry codebase which would be a learning opportunity.
Project mention: Methods and processes for reduce bugs in production | news.ycombinator.com | 2023-08-24>As now we've introduced some peers code review, automatic testing on most critical stuff (but since the codebase sucks these aren't really reliable tests)
They may not be "reliable", but these are your safety net, or harness, so you don't fall. I wrote about similar issues, for instance here: https://news.ycombinator.com/item?id=26591067 and, given your promotion, here: https://news.ycombinator.com/item?id=37211796. It contains a few steps starting from "So...".
You can add monitoring, something like Sentry (https://sentry.io) will capture exceptions that were not handled that you have not seen because the stack trace is buried in hundreds of pages of logs or something. It groups them by exception and counts them. It's pretty awesome. (https://docs.sentry.io). It supports around 108 platforms (Java, Python, JavaScript, etc.). This lets you see the exceptions and makes prioritizing easier (which ones are the most frequent, which ones impact the most, etc.).
If you don't have them already, issue templates are really useful and the comment I linked to explains why, but here's an example of an issue template (again, you can configure them for different types of issues so team members select from a dropdown for a bug or a feature):
- it entirely removes a class of discussion of "opinion" on style. Tabs or spaces? Import ordering? Alignment? Doesn't matter, use go fmt. It's built into the toolchain, everyone has it. Might it be slightly more optimal to do X? Sure, but there's no discussion here.
- it hits that sweet spot between python and C - compilation is wicked fast, little to no app startup time, and runtime is closer to C than it is to python.
- interfaces are great and allow for extensions of library types.
- it's readable, not overly terse. Compared to rust, e.g. [0], anyone who has any programming experience can probably figure out most of the syntax.
We've got a few internal services and things in Go,vanr we use them for onboarding. Most of my team have had PR's merged with bugfixes on their first day of work, even with no previous go experience. It lets us care about business logic from the get go.
[0] https://github.com/getsentry/symbolicator/blob/master/crates...
[Sentry.io](http://Sentry.io) | Senior Software Engineer, Storage | ONSITE (San Francisco or Seattle, 3:2) | Full-time
[Sentry.io](http://Sentry.io) builds a suite of application monitoring tools that developers love. The Search and Storage team builds out high-volume ingestion (hundreds of thousands of records per second) for our near-real-time event and metric storage built on top of the columnar data store ClickHouse. We’re looking for a seasoned engineer who has dealt with high-volume, production-traffic serving systems who’s searching for a new challenge.
The vast majority of our work is source-available; come take a look at what our team is working on at https://github.com/getsentry/snuba. Note that this position does have an on-call component.
E-mail me, the hiring manager, at [email protected] to learn more.
It's probable the core will always remain closed. That's both a business and practical decision. However, much like how Sentry have some of their services open-source, we may follow that route.
tag-production related posts
Index
What are some of the best open-source tag-production projects? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | Sentry | 36,957 |
| 2 | sentry-javascript | 7,635 |
| 3 | self-hosted | 7,284 |
| 4 | responses | 4,042 |
| 5 | sentry-python | 1,741 |
| 6 | sentry-java | 1,097 |
| 7 | Raven Ruby | 915 |
| 8 | sentry-cli | 875 |
| 9 | sentry-cocoa | 765 |
| 10 | sentry-dart | 715 |
| 11 | sentry-symfony | 679 |
| 12 | raven | 599 |
| 13 | sentry-rust | 568 |
| 14 | Sentry | 563 |
| 15 | symbolic | 432 |
| 16 | sentry-native | 363 |
| 17 | symbolicator | 339 |
| 18 | snuba | 318 |
| 19 | spotlight | 297 |
| 20 | relay | 293 |
| 21 | sentry-electron | 217 |
| 22 | rust-sourcemap | 213 |
| 23 | sentry-unity | 188 |
Sponsored