benthehenten
Joined 12 years ago
Karma
97
Submissions
34
Member since
Sep 15
Co-Founder of https://logrocket.com
View on Hacker NewsRecent submissions
Comment · 7 years ago
LogRocket | Cambridge, MA | Boston, MA | Full Time, Onsite | https://logrocket.com
LogRocket is a front-end monitoring service that helps developers fix problems in their web apps by letting them replay bugs. Our product is used by thousands of companies like Brex, Bloomberg, and Reddit to eliminate the guesswork for developers as they fix bugs and user-reported issues. We are a few engineers today and looking to double our team in the next few months. If you are interested in joining at the ground-floor of a venture-funded, fast-growing company, feel free to reach out to ben at logrocket dot com.
Comment · 8 years ago
At LogRocket (https://logrocket.com) we've been on GCP for ~2 years and have been extremely satisfied. Some reasons in particular:
- "Infinitely scalable" services like Bigtable and Cloud Pub/Sub have helped us scale extremely quickly to support large clients.
- The durability of Cloud Pub/Sub was particularly important early on as it served as a fail safe when our consumers would go down
- Aggressive discounts for committed use. For our particular workload we've calculated AWS could be as much as 10% more expensive
- Dashboard developer experience and UX is more approachable than AWS
Comment · 8 years ago
I'm not sure about the implementation in Session Stack, but I work at LogRocket (https://logrocket.com) where we're solving a similar problem. We use a few methods to ensure that we have a minimal overhead on performance.
- We use worker threads for data encoding and network I/O
- We use the MutationObserver API for capturing diffs of the DOM
- We pull static resources directly from an application's servers (vs uploading from the client)
- Loading method shims first (and later the rest of our SDK asynchronously) to reduce initial loading time
- Batching requests and waiting for network downtime to send data
- We use Protobufs as a wire format for reducing bandwidth
I'm sure Session Stack employs some similar techniques- would be curious to hear about methods they're using as well.
Comment · 8 years ago
If you're looking to get more context on exceptions in JavaScript, you could try LogRocket (https://logrocket.com). Similar to how Crashlytics' breadcrumbs feature records user actions leading up to a crash, LogRocket records user actions, network requests, console logs, DOM, and application state in web apps.
[disclaimer: I work at LogRocket]
Comment · 8 years ago
In the long term, it's definitely something we plan to do. For now, we are prioritizing building new features and improving the core product.
Doing open source well requires significant resources for community management, PR review, and support. When we do release an open source version of LogRocket, we want to be sure that we can dedicate enough time to supporting our users and engaging the community.
(I work at LogRocket)
Comment · 8 years ago
(disclosure - I wrote this article and work at LogRocket)
The product is built-out in the sense that we have many customers who use LogRocket daily to fix bugs and support their users.
Of course we've only just started toward our long term goal and have lots more work to do!
Comment · 9 years ago
So far, we've worked with a few larger customers to run LogRocket on their own infrastructure (or their own AWS environment in some cases), but we haven't publicized the specifics yet.
If you shoot me an email (ben at logrocket) I'd be happy to discuss in more detail :)
Comment · 9 years ago
I'm on the LogRocket team.
Your concern is fair, though many modern analytics tools can capture PII if not properly configured. It is important when using any such tools, including LogRocket, that developers understand the scope of the data collected and properly censor things like SSN, Credit Cards, or health data.
Some of our more security-conscious customers also just run LogRocket on their own servers with our self-hosted version. In this case, the script becomes first party, and they can configure behavior where no data leaves the client unless a user specifically gives permission.