highlight
symbolicator
highlight | symbolicator | |
---|---|---|
33 | 6 | |
6,944 | 339 | |
3.0% | 0.9% | |
9.9 | 9.3 | |
1 day ago | 6 days ago | |
TypeScript | Rust | |
GNU General Public License v3.0 or later | MIT License |
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.
highlight
- Show HN: An open source performance monitoring tool
-
Show HN: Using LLMs and Embeddings to classify application errors
[2] https://app.highlight.io/error-tags
-
Show HN: HyperDX – open-source dev-friendly Datadog alternative
[2] https://github.com/highlight/highlight/tree/main
-
Launch HN: Highlight.io (YC W23) – Open-source, full stack web app monitoring
We have an SDK request here: https://github.com/highlight/highlight/issues/4225
We don't have a particular leaning towards javascript, but haven't gotten to PHP yet. We're definitely open to contributors, but otherwise, we can hopefully get to this in the coming months.
-
Highlight.io (YC W23) – open-source, full stack web app monitoring
Hi Hacker News! We’re Jay and Vadim from Highlight.io (https://highlight.io). We’re building a truly open source [1] observability platform for modern web applications. We posted some of our tools to HN in recent months [2][3]. Today, we’re excited to formally launch the project, share more about where we’re going, and of course, poll the community for some feedback.
A bit of background: Vadim and I have worked at quite a few startups at this point, and a recurring challenge we’ve faced was tracing usability issues on the frontend to downstream errors and logs on the server. Understanding the real reason behind customer issues was always a chaotic juggling of multiple tools. With the rise of "frontend-forward" frameworks such as NextJS, which blur the boundary between the client and server, the complexity of tracing these issues is only growing.
This is where Highlight.io comes in: our product bridges the gap between client and server to give you a holistic view of your entire application.
At its core, Highlight.io has three main “products”: Session Replay, Error Monitoring, and Logging. The novelty here is not in each product but in how they are connected. For example, in Highlight.io it’s very easy to click from a given error to the associated user session where it is thrown [4], and from a given error, you can easily inspect all of the logs that fired leading up to it. Ensuring that all of our products work together seamlessly with little to no effort is a core principle of our product strategy. If you’re using a common framework [5], for example, we’ll automatically link your frontend sessions with backend errors and logs. No agents, configuring facets, or anything else, It just works.
We depend on several open source projects that help us move quickly. OpenTelemetry (OTEL) [6] is one of them, which helps us with maintainability, i.e. for every language that we support, we only maintain a thin wrapper around its respective OTEL SDK. OTEL is also a great way to enable the community to contribute, and we’re already seeing traction in this space (ie. an open source contributor built a wrapper for a Java SDK [7]).
rrweb [8] is another project we leverage heavily for our session replay product. It drives our ability to record and replay the DOM to visualize user flows in the frontend. We’ve had the privilege to work closely with the rrweb team to ship improvements, and we’re now actively sponsoring the project [9].
ClickHouse [10] has recently become a loved database on our team, as we historically used Opensearch for search-heavy workloads and started to hit growing pains with ingest throughput. We recently rolled it out for our logging product [3] and plan to replace our sessions and errors (and upcoming tracing work) with the database as well.
From a business perspective, Highlight.io is open source under the Apache 2.0 license, and we make money with our hosted product [11]. For the hosted product, you can set billing caps for each offering and we don’t charge for seats. At this point, we have 100+ companies paying for our product (some of which are large enterprises), and thousands of sole developers use Highlight.io every week.
On our roadmap [12] for the future includes metrics, tracing, release management and more. We also are launching several updates this week on our launch week page [13].
Overall, we’re excited to be sharing Highlight.io with the world, and Vadim and I are particularly excited to get some feedback from the HN community. Please give us a test-drive at https://app.highlight.io and let us know what you think. We would love to learn about what you wish you had in an observability product as well as any other experiences and ideas in this space. We look forward to hearing from you!
-
What are some really good open-source next js projects in productions that you can study from?
https://gitlab.com/hyperlink-academy/app https://github.com/highlight/highlight https://github.com/calcom/cal.com https://github.com/Nutlope/roomGPT
-
OpenObserve: Elasticsearch/Datadog alternative in Rust.. 140x lower storage cost
I'd be curious to hear how this compares to
https://qryn.metrico.in
and
https://github.com/highlight/highlight
(There are some interesting comparisons/comments vs signoiz in sibling threads).
-
Building a Type-Safe Tailwind with vanilla-extract
We only scratched the surface of vanilla-extract here, so check out the documentation if you’re interested in learning more. We’ll continue to share about how we are leveraging it to build the Highlight design system, and all our code is open source if you’re interested in exploring our usage more. All the code for the examples in this article are also available for anyone to fork and play around with as well.
symbolicator
-
Practical nil panic detection for Go
- 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...
-
This isn’t the way to speed up Rust compile times
> Aren't they slower or about as slow as C++, which is notorious for being frustratingly slow, especially for local, non-distributed builds?
Yes. Significantly slower. The last rust crate I pulled [0] took as long to build as the unreal engine project I work on.
[0] https://github.com/getsentry/symbolicator/
-
Launch HN: Highlight.io (YC W23) – Open-source, full stack web app monitoring
2022: https://blog.sentry.io/we-just-gave-260-028-dollars-to-open-...
In addition to that, there are contributions to open source done in the form of code that is, open source, such as the symbolication service: https://github.com/getsentry/symbolicator and many others: https://github.com/getsentry/
- Introduction to Sentry Symbolicator
-
Seed – A Rust front-end framework for creating fast and reliable web apps
Digging up the topic, I also found that new framework https://github.com/tokio-rs/axum, which already seems to be popular.
Sentry is rewriting some of their libs from Actix to Axum: https://github.com/getsentry/symbolicator/commit/b6ef7cb00b7...
-
What’s up with these new not-open source licenses?
Disclosure: I work at Sentry.
> My personal term for this sort of "We're OK with little people using the software but we don't want any competition"
Large companies are free to use Sentry. There are Fortune 50 companies running Sentry at scale internally without paying us a cent. That's totally cool.
You're also free to compete with Sentry. You're not free to repackage Sentry for the purposes of competing us. There are lots of competing error and performance monitoring products out there that do perfectly fine without it.
I should also note that many components of Sentry are distributed with OSI-approved licenses that you are free to use to compete with us. For example, our Symbolication service (https://github.com/getsentry/symbolicator) ships with an MIT license, and it's an important part of our business.
What are some alternatives?
openobserve - 🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces, RUM, Error tracking, Session replay).
pgbouncer-fast-switchover - Adds query routing and rewriting extensions to pgbouncer
PostHog - 🦔 PostHog provides open-source product analytics, session recording, feature flagging and A/B testing that you can self-host.
rust-rdom - 🍂 A Rust-based simulated DOM (browser-independent replacement for web_sys)
rrweb - record and replay the web
sycamore - A library for creating reactive web apps in Rust and WebAssembly
hyperdx - Resolve production issues, fast. An open source observability platform unifying session replays, logs, metrics, traces and errors powered by Clickhouse and OpenTelemetry.
pinwheel - Pinwheel is a library for writing web user interfaces with Rust.
audiolm-pytorch - Implementation of AudioLM, a SOTA Language Modeling Approach to Audio Generation out of Google Research, in Pytorch
dropshot - expose REST APIs from a Rust program
openobserve-chart - Simplified Helm chart for single-node OpenObserve
sauron - A versatile web framework and library for building client-side and server-side web applications