HN user

th0th

30 karma

https://www.webgazer.io

Posts5
Comments19
View on HN

Yep, Prosody was one of my failed attempts :P I am running everything on a kubernetes cluster, so a maintained helm chart is the first thing I check when running something. I didn't have much luck with XMPP servers with this.

That IMAP auth trick is really awesome thinking BTW, kudos!

Not really, I didn't have any delivery-related issues, and didn't get any complaints from other people as well. I have mixed feelings towards Matrix due to;

1. The only stable and maintained implementation is "matrix-synapse" and it is written in Python.

2. The most commonly used client is "element", and it is governed by the same people. So it feels we are the mercy of a single company.

I wanted hard to go with a more established protocol like XMPP but failed to get a server running properly :)

It feels really nice to see stuff like this while the most of the people think Slack, Discord and a few others are the only choices.

I recently went through the hassle of deciding on something small for my family + company circle. Mainly considered XMPP and Matrix, and went with Matrix. Didn't know there was such a thing as "always-on" on IRC tho.

Hey folks,

I built the free and open source, privacy-first PoeticMetric Analytics. It has both SaaS and self-hosted options. Source code is available on https://github.com/th0th/poeticmetric.

Its stack includes; PostgreSQL for the single source of truth database, ClickHouse for time series data, RabbitMQ as the task queue, and Golang for the backend. On the frontend, I use React (Next.js, typescript and bootstrap) for a modern user experience.

No personal data is collected. And it doesn’t use any persistence stuff like cookies, local storage, etc.

I would love to hear your thoughts and feedback. Cheers!

Hi @heliodor, WebGazer founder Gokhan here :)

Actually the site is running but not accessible due to the issue. Glad you got the heads up, after a while I had to pause monitoring to prevent side effects.

I have been working on WebGazer (https://www.webgazer.io) since 2015 and even if the stack got bigger with time, it has Django in its foundation :)

It started as a simple website monitoring product and evolved from there. It enables customers to monitor websites, REST APIs and cron jobs on the same platform. I also added status page functionality (e.g. https://status.webgazer.io) some time ago.

I have a day job but I keep building and hustling at the side. We live off of paychecks from our day jobs but live for our side projects, don't we? :P

I have been developing web stuff for about 10 years. The dilemma I experienced about monitoring is that when you do your own monitoring you need to make sure your monitor is working, too. Relying on an external platform sounds saner when I consider this. This is why we consider WebGazer "mission critical".

Hi, this is Gokhan from WebGazer Team. Thanks for the comment, we are aware of the availability of cheaper services. As a matter of fact, some of them are the reason we started WebGazer.

Alerting is a basic thing and it is done kind of OK by some others. But true analytics is hard to get, we are still working on providing better reports. As an obvious plus, we provide status pages we produce by the monitoring data collected. This is for not making you depend on another service just for a status page.

Also, we are looking for ways to make WebGazer a complete monitoring and analytics platform. Plans still aren't very clear but server monitoring or client-side analytics are some things we have in mind.