metriport
highlight
metriport | highlight | |
---|---|---|
7 | 33 | |
369 | 6,968 | |
2.7% | 3.7% | |
10.0 | 9.9 | |
4 days ago | 4 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | 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.
metriport
-
Show HN: HyperDX – open-source dev-friendly Datadog alternative
This could be huge for healthcare companies like Metriport [1] - do you sign BAAs with customers for HIPAA compliance?
[1] https://github.com/metriport/metriport
-
Open-source API for integrating with Garmin devices
For any developers here - we recently released an open-source API that allows you to pull data from Garmin devices.
- Metriport: Open-source and universal API for health data
- Show HN: Metriport – Open-source universal API for health data
- Show HN: Metriport – open-source universal API for health data
-
We just launched an OSS Health Devices API to help developers gain access to their users’ health data from various wearables, RPM devices, and mHealth apps.
We just launched an open-source API on GitHub that allows developers to gain access to their users’ health data from various wearable, RPM device, and mHealth app sources. After building a health app ourselves previously, we wanted to make the open-source product we wish existed when we were developing our app. We thought it would be useful to share the API here, as many developers in the healthtech space could potentially benefit from it.
-
An update from the Metriport team
This being said, we will not be shutting down the app. We have no intentions to kill the project, and in fact are hoping to be able to implement our newly developed and open-source Health Devices API into it at some point, which will allow app users to connect to sources such as Fitbit, Garmin, Oura, Whoop, Withings, and Cronometer, with more integrations on the way. Once we can find the development time to do this, we will push out an update and send out an email announcement to confirm this.
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.