PostHog VS Sentry

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.

Posthog. Posthog has a lot of sub products but I use it mainly for analytics and session replays. I have to say Posthog is an impressive product. Everything from dev experience to dashboards is just awesome. Great to see GA finally got some real competition. I'm looking forward to try all the other products from them.

Visit Posthog Website and signup to create your account using either email, google, or github etc.

We use tools like Posthog to measure how users are using our products. This allows us to see what features are being used and which ones are not.

I tried a few open source bug trackers, but from what I found they look either very old (https://www.bugzilla.org/) or super heavy (https://sentry.io). Bugsink provides a nice middle ground so I encourage you to give it a try.

For production JS (both browser and server), consider an error-tracking tool (like Sentry). These capture exceptions with stack traces from real users, so you can debug live issues remotely.

Use distributed tracing: Tools like Sentry, Datadog, and New Relic are serverless-friendly.

Structured logging transforms debugging by providing a detailed, searchable record of an application’s state, including variable values, stack traces, and user actions. According to Gartner, organizations with robust logging systems resolve production issues 40% faster. Doug Crawford, President and Founder of Best Trade Schools, highlights their value: “Implementing a structured logging system… makes isolating the problem straightforward.” Tools like Sentry for real-time error tracking, Log4j for Java applications, or ELK Stack for log aggregation enable developers to pinpoint issues quickly, reducing the need for manual reproduction. For example, Sentry’s breadcrumb feature captures user actions leading to an error, offering a clear debugging trail.

Sentry is built for developers who want to catch and fix application bugs quickly. With code-level visibility and performance monitoring, it’s perfect for SaaS teams prioritizing quality and stability.

Monitoring/Recovery: Prometheus, Grafana, Sentry, New Relic

In this tutorial, we'll explore how to build a text-to-image NSFW AI image generator using Next.js, integrate it with Sentry for error tracking, and leverage Webpack for module bundling. We'll also discuss best practices to ensure that our application runs smoothly in a production environment.

Late to the party here but we (Sentry) have been using ECharts since 2018 (https://github.com/getsentry/sentry/pull/9072) and still holding strong!

[auth] token=xxx [defaults] url=https://sentry.io/ org=woai3c project=woai3c