Our great sponsors
-
highlight
highlight.io: The open source, full-stack monitoring platform. Error monitoring, session replay, logging, distributed tracing, and more.
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
signoz
SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
-
-
openreplay
Session replay and analytics tool you can self-host. Ideal for reproducing issues, co-browsing with users and optimizing your product.
-
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.
-
-
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!
1: https://github.com/highlight/highlight/blob/main/LICENSE
2: https://news.ycombinator.com/item?id=34897645
3: https://news.ycombinator.com/item?id=35643255
4: https://youtu.be/EvGsmbt0F7s?t=65
5: https://highlight.io/frameworks
6: https://opentelemetry.io/
7: https://github.com/highlight/highlight/pull/4812
8: https://github.com/rrweb-io/rrweb
9: https://github.com/rrweb-io/rrweb#gold-sponsors-
10: https://clickhouse.com/blog/overview-of-highlightio
11: https://highlight.io/pricing
12: https://www.highlight.io/docs/general/roadmap
13: https://highlight.io/launch-week-2
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!
1: https://github.com/highlight/highlight/blob/main/LICENSE
2: https://news.ycombinator.com/item?id=34897645
3: https://news.ycombinator.com/item?id=35643255
4: https://youtu.be/EvGsmbt0F7s?t=65
5: https://highlight.io/frameworks
6: https://opentelemetry.io/
7: https://github.com/highlight/highlight/pull/4812
8: https://github.com/rrweb-io/rrweb
9: https://github.com/rrweb-io/rrweb#gold-sponsors-
10: https://clickhouse.com/blog/overview-of-highlightio
11: https://highlight.io/pricing
12: https://www.highlight.io/docs/general/roadmap
13: https://highlight.io/launch-week-2
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!
1: https://github.com/highlight/highlight/blob/main/LICENSE
2: https://news.ycombinator.com/item?id=34897645
3: https://news.ycombinator.com/item?id=35643255
4: https://youtu.be/EvGsmbt0F7s?t=65
5: https://highlight.io/frameworks
6: https://opentelemetry.io/
7: https://github.com/highlight/highlight/pull/4812
8: https://github.com/rrweb-io/rrweb
9: https://github.com/rrweb-io/rrweb#gold-sponsors-
10: https://clickhouse.com/blog/overview-of-highlightio
11: https://highlight.io/pricing
12: https://www.highlight.io/docs/general/roadmap
13: https://highlight.io/launch-week-2
Happy to help there - looks like you are missing the docker compose v2 plugin (https://docs.docker.com/compose/).
You should check out SigNoz - https://github.com/signoz/signoz
We are not specifically focused on web app monitoring, but you should be able to monitor web app easily, esp. if you want to also monitor backend services and have frontend in JS
And, yeah - we have all the docs for self hosting - https://signoz.io/docs/install/
Docs for Angular apps - https://signoz.io/docs/tutorial/instrumenting-angular-fronte...
For context, this project is a smallish backend(~10 endpoints) running on CF workers with a low volume of logs.
The goal for now is to get something basic working, since cf workers don't log by default and I need to track down a bug.
These assessments were made quickly, so they may not be accurate, but here they are anyway:
Logflare -
A js client library (https://github.com/Logflare/winston-logflare) has 2 high vulnerabilities, still uses commonjs imports in the example, last update 3 years ago. The latest tweet in the testimonials section of their home page is from 3 years ago. They were acquired a few years ago, so is the product just moldering? Or maybe they are just focusing on working with Supabase? In either case, not great for my case.
Log Push - I got this set up, but the logs were in a unknown binary format(or corrupt?). Even if is was working, the logs would be in R2, without great support for query/search/presentation etc. Not sure exactly what the problem is, but the feature feels a bit new/beta and the "upside" is kind of low.
Sentry’s license change on the fork was a mistake. It has been fixed though: https://github.com/getsentry/rrweb/pull/92
The fork exists as a ‘buffer’ to get some changes (features or bug fixes) out without the need to couple with the npm release of rrweb itself. Sentry engineers have several PRs in upstream rrweb merged and the goal is to increase the upstream contributions and close the gap between our fork and upstream. We’re currently porting our changes from v1 to the v2 branch.
I believe Sentry has made financial contributions to rrweb but directly to a maintainer. I'll let others who know details to comment on this. I'm sure more contributions will be done, as this is very much in the interest of Sentry anyway.
Worth noting, Sentry has been making larger contributions to OSS every year, as the company grows:
2021: https://blog.sentry.io/we-just-gave-154-999-dollars-and-89-c...
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/