New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Uptime Monitoring
Hello,
I'm conducting a survey to gather some information for my project (uptime.buzz).
I want to tailor the service to meet the community's requirements, so kindly answer the following questions if possible, thanks!
- What uptime monitoring service are you using currently?
- How many websites are you Monitoring?
- How much money are you spending on it, monthly/annually?
- What do you think should be an ideal price for such service?
Thanks!


Comments
Hetrixtools
8
0
To be honest, 0, otherwise I'd set up such service by myself...
I) Uptime kuma on fly.io
II) 30 websites and servers
III) 0
IV) 0
why not hetrix? do we get free credits monthly on fly.io? ~ I don't see an option like this though
Uptimerobot
i'm self-hosting uptime kuma, so it's free. monitoring 9 servers currently.
Betterstack and Beszel.
Can’t say without having tested the tool
Currently Uptime Kuma, although I wish they had a first party API. Recall reading that might happen with 2.1. Would like to automate via ansible the creation of monitors. Didn’t have much luck with some quite old third party attempts of an API.
Endpoints are also in Beszel but not currently using for alerting.
Hetrix get 15 monitors in free plan with 1 minute or more checking frequency, uptime kuma open source no limits no monitors or checking frequency, as for fly.io I have the legacy hobby plan which was technically free for 3 micro instances. They have since stopped offering the plan, but there are few alternatives as well like koyeb, etc. or I can just utilise my stardust instance coupled with dns64 or CF warp for my use case of fly.io discontinued the free micro instances.
1.zabbix for server, uptime kuma for websites.
2.4 servers, 3 websites.
3.0(if not counting vps price)
4.0 unless you are competitive.
Prometheus + blackbox_exporter
3 websites, 5 servers
€3.79 for VPS
I have 600ms checks and fast alerting is a must for commercial service IMO
A combination of batter stack, hetrixtools and Zabbix
Thank you everyone for your input!
The SaaS will definitely have a forever free plan. The product is still in development phase and will take a few months to move to alpha or beta phase.
Along with uptime monitoring, I'll also add more features like, dns monitoring, or ttfb monitoring etc in the same niche.
You can also suggest features you might like!
Thank you all for your valuable time!
Services: Hetrixtools, Pingdom
Selfhosted: Icinga, Nagios/Naemon, Check MK, Beszel, various solutions built on Grafana/Influx/Prometheus etc.
Websites is probably no more than 10-15.
Nodes and servers probably a bit above 10k.
I'm not the one paying the bills so unsure, but I think Hetrix is like $20 a month and Pingdom like $100 per year.
The rest is selfhosted so it costs time and infrastructure, hard to calculate.
I think you have to be more specific about what you plan to provide.
In my opinion Hetrixtools are among the best and their free tier more then covers most peoples needs, so you have to have something really special to be able to even charge for it. If you have everything Hetrix has, look at their pricing and it should give you an idea.
I'm using hetrix myself! I too think they have an amazing free tier. The only thing I don't like about hetrix is the UI.
Man of culture.
alerts.net
Something I might note, is the majority of what I monitor is internal servers behind a VPN that have public inbound traffic blocked, however they can communicate out to the internet. Things like my personal backups ect. I still want to know its up, but whether you call it a ‘website’ or not, I dunno, Its a web app but not public facing.
I also use UpTime Kuma to track whether my rustic backups are running by having a ‘push’ to a listening probe on success/fail, and multiple missed ‘push’ notices or a message with an error in it, will then trigger an alert that something is up.
Both these cases are more concerned with ‘push’ style probes rather than http request so for any service I’d want that as an option.
Might be worth seeing what other probes people like to use that aren’t just a standard http get request.