sentry-javascript VS PostHog

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/... )

Sentry JavaScript - Sentry, renowned for its comprehensive solutions in frontend monitoring and error logging, recently adopted Nx for their official JavaScript SDK. This move integrates Nx's capabilities into their monorepo, containing packages for popular frontend and Node.js backend integrations. They also published a blog post on the benefits they've seen following the adoption of Nx in their monorepo (hint: reducing CI times by 35%).

We've just started this initiative and have already been able to help Sentry get optimized with task caching and task pipeline optimizations for their workspace!

In addition to the network call data we already attached, that does go through data PII scrubbing on the edges as you mentioned, we're discussing capturing request/response body. We even talked about it today: https://github.com/getsentry/sentry-javascript/issues/7103

Avoiding any PII from getting into the system is always top of mind. And we're considering this as an opt-in regardless of scrubbing on the edge ingestion service.

Add Sentry’s Next.js SDK to your next.js projects.

Get started with Sentry for Electron and drop us a line on GitHub, Twitter, or our Discord. And if you’re new to Sentry, you can try it for free today or write to [email protected] to get started.

Great idea! #4118

PostHog analytics you can self-host (great for privacy)

For monitoring, there are separate full-fledged monitoring solutions like Opik, PostHog, Langfuse or OpenLLMetry, maybe will try some next time.

Posthog is pretty good but very pushy towards using their SaaS (understandably). Self hosting is not really advertised on their main site however is buried in their gh repo as a footnote [1] with indications of vague issues past 100K events/month. Haven’t delved into how to scale it past that though and they do provide some docs that I have yet to review.

Also the primary repo is not FOSS, and that "100% FOSS" repo is buried in yet another footnote [2].

Plausible follows in PH footsteps but is not fully faithful to open source. If you want to self host, you won’t have same set of features as their SaaS and need to rely on long term releases for their "community edition" [3]

On "Ahrefs", is there even an open source version of their product? I couldn’t easily find it (on mobile). [4]

Maybe I’ll take a look at others you mentioned later but if rybbit can remain faithful to their FOSS roots then I think there’s a real chance of it becoming huge.

For thosw that don’t want to self host (mostly corporate shitholes), rybbit can milk them with their managed SaaS product.

[1] https://github.com/PostHog/posthog?tab=readme-ov-file#self-h...

[2] https://github.com/PostHog/posthog?tab=readme-ov-file#open-s...

[3] https://github.com/plausible/analytics?tab=readme-ov-file#ca...

[4] https://ahrefs.com/

I'm unable to see their website

https://posthog.com

Is it just me?

Website link: PostHog

Send events to analytics tools like PostHog.

For SaaS startups looking for a powerful, privacy-conscious analytics platform, PostHog provides an all-in-one solution designed for modern product teams.

The next rung up are User recordings. For users that are having issues, we have concrete recorded data for their flow. The flows would include anything relevant to the application, how they used it, what actions they took. All so we can actually see what happened in context for when there is a problem. No one wants to spend any time looking at recordings if they don't have to. It is also very difficult to identify the root cause of problems by reviewing a recording, but having them is indispensable to your support engineers when they need them, when a user has reported a issue. Solutions include PostHog, FullStory, Sentry. If you don't have these recordings, then the next best alternative (which is very far away) is getting a live screencast from the user. These are less useful, and more expensive to obtain. Worst of all, they can and have been used to breach sensitive systems.