Chartbrew VS GoAccess

I'm working part-time on my project https://chartbrew.com

It's an open-source data visualization and reporting platform that I started in 2018, I abandoned in 2019, then resumed working on it more seriously in 2020.

Currently, the platform is doing $1,138 in MRR from then managed hosting service and has made over $11k in revenue so far. It's been growing steadily in the last few months but going through a rough Dec-Jan period at the moment. You can see the open page at https://chartbrew.com/open

Onwards and great job everyone at working to make side projects work for you!

Chartbrew (server): Chartbrew is open-source reporting service which really makes it easy to visualize data.

Chartbrew can fetch data from databases and other data sources. Then the user can create dashboards to visualize and explore this data as Metabase does it as well.

Lots of great mentions here. You can also check out Chartbrew. It's open-source and can be self-hosted for free. It doesn't have an open core, so all the features are available out of the box.

One use-case that the platform is being used for is for B2B SaaS businesses to offer their analytics through Chartbrew. So it is possible and there are people already using it like this.

Or if you're wondering if you can offer the analytics platform by itself as a SaaS, I built a SaaS layer on top of it here: https://chartbrew.com

If one wants server-side metrics with a little more info than the author's "hacky little script", there's always goaccess [1], which functions in broadly the same way. I even use it with Firebase Hosting-hosted sites via [2] (which I wrote).

[1] http://goaccess.io/

[2] https://github.com/Silicon-Ally/gcp-clf

> Just use GoAcces for fuck's sake.

GoAccess seems pretty cool and is probably a good task for the job, when you need something simple, thanks for recommending it: https://goaccess.io/

Even if you have analytics of some sort already in place, I think it'd probably still be a nice idea to run GoAccess on your server, behind some additional auth, so you can check up on how the web servers are performing.

That said, I'd still say that the analytics solutions out there, especially self-hostable ones like Matomo, are quite nice and can have both UIs that are very easy to interact with for the average person (e.g. filtering data by date range, or by page/view that was interacted with), as well as have a plethora of different datasets: https://matomo.org/features/

I think it can be useful to have a look at what sorts of devices are mostly being used to interact with your site, what operating systems and browsers are in use, how people navigate through the site, where do they enter the site from and how they find it, what the front end performance is like, or even how your e-commerce site is doing, at a glance, in addition to seeing how this changes over time.

People have also said good things about Plausible Analytics as well: https://plausible.io/

I heard about https://goaccess.io/ (and even tested it) but first, nothing about tracing logs, and I think that the provided HTML dashboard isn't enough security-oriented for me but it's more about monitoring your customer volume... It does -partially- fit my case.

Loved AWStats! Still can be useful — but bots, client side caching, CDNs, and did I mention bots..? have made the data hard to rely on for much. A while ago I switched from AWStats to GoAccess (https://goaccess.io/) for this kind of thing. I prefer its interface, and it's way way faster to churn through big log files (C vs. Perl).

matomo and goatcounter are nice, but there are even solutions which don't need any extra CPU or any extra client request:

• https://goaccess.io/

• https://www.awstats.org/

Both of them are free/open-source.

I was looking something for like that a while ago and the closes I can was goaccess, but it did not have IPv4/IPv6 feature. https://github.com/allinurl/goaccess/issues/1492

I use this to monitor my reverse proxy (SWAG) and fail2ban logs in conjunction. It's not as streamlined as GoAccess, GrayLog, Grafana, etc . . . but it is very personal. I divide all my connections into three buckets: Home, Outside, and Known Devices; and fail2ban statistics are layered against the all connections.

Somewhat off-topic: goaccess does look very appealing.

https://goaccess.io/

All panels and metrics are timed to be updated every 200 ms on the terminal output and every second on the HTML output.

Logfile analyse komplett ohne cookies und ohne 3rd parties. https://goaccess.io/