Live data from Hacker News

Ask HN: How do you monitor your websites?

news.ycombinator.com

71–80 of 104 posts

Re: Ask HN: How do you monitor your websites?

#71
DataDog, our API is 100% serverless microservices (aws lambda) and 90% of them connect to elasticsearch / dynamo. If we start getting high error rates an alarm goes off and slack / email lights up. We are monitoring upwards of 300 lambda's this way.

Re: Ask HN: How do you monitor your websites?

#73

To piggy back on the question, has anyone had a good experience using Prometheus and Grafana for monitoring? I'm looking into trying it. I've looked into Zenoss but from what I gather it's slow.

Another happy user here. Only we use Telegraf to gather the metrics on the servers, I've found that it's a bit more flexible than the normal node exporter.

For alerts we have a mix of grafana and AlerManager.

Re: Ask HN: How do you monitor your websites?

#74

Once every few months, I go to the website.

Guess I'm not the only one, and of course my personal site was down for the last three days because the domain registration had expired and couldn't be renewed on an outdated card.

I facepalmed.

But once my setups get a bit more complex I was thinking I'd build webhooks into an analytics server, and ping those from each server with a json request which includes health data for each's databases and other servers.

I'm no where near that so I'll probably sign up for the free plan on uptimerobot later mentioned in other comments.

Re: Ask HN: How do you monitor your websites?

#77

TICK stack: Telegraf, Influxdb, Chronograf, Kapacitor. They're have a massive array of plugins that can watch/store/graph/alert on just about anything. https://www.influxdata.com/time-series-platform/

I agree with this. I just set this up at work and it's really cool. Still in active development and not fully mature yet, but gets the job done and is pretty good quality.

I wish the documentation was better but telegraf's documentation is light years ahead of collectd, which is similar software.

Kapacitor needs some more examples and the default Chronograf-generated TICKscript needed to be thoroughly modified to meet my needs. It took me way too long to figure out how to use stateChangesOnly() to prevent me from getting constant notifications once something went into an alarm state.

That said, the stack works well, even if it has a few rough edges. Thanks to Influxdata for the open source stuff. High quality open source software makes me want to endorse them and purchase the paid products.

Re: Ask HN: How do you monitor your websites?

#78

TICK stack: Telegraf, Influxdb, Chronograf, Kapacitor. They're have a massive array of plugins that can watch/store/graph/alert on just about anything. https://www.influxdata.com/time-series-platform/

I agree with this. I just set this up at work and it's really cool. Still in active development and not fully mature yet, but gets the job done and is pretty good quality. I wish the documentation was better but telegraf's documentation is light years ahead of collectd, which is similar software. Kapacitor needs some more examples and the default Chronograf-generated TICKscript needed to be thoroughly modified to mee…

Agree on the TickScript criticism! Just not enough stack overflow answers to go around. Btw, stateChangesOnly() can take a time argument which is really really handy!

Re: Ask HN: How do you monitor your websites?

#80
Answering the second part of your question:—

Re SSL expiry: we've taken the route of running VirtualMin on our 'commodity' servers, sites setup in there have an auto-renew policy if they use SSL, so it requires no action and auto-updates whenever certs expire (IIRC it's every three months? but I might be wrong: it requires no thought nor action from me).

For domain names, we use Joker (Swiss company), we've found them to be good in all aspects, and they send renewal notices well in advance (including a link that anyone can use to renew the domain, even without having an account with them).

Uptime monitoring is a whole different kettle of fish, and we manage it on a per client basis depending on needs. For the sites we host, generally if the server's up, then the sites are up — but we also do more specific monitoring if it's a client requirement.

Post reply on HN