![\"woozweb\"](\"https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2016\/05\/woozweb.png\")
<\/a>woozweb<\/p><\/div>\n
In the last few years, I worked for Smile, a french Open Source integrator. Among other things, Smile hosted Woozweb, a free service allowing you to define HTTP checks, firing\u00a0mail notifications.<\/p>\n
Since I left Smile, I’ve opened an account on Woozweb, and used it looking after public services I manage, checking them from outside my facilities.
\nTwo days ago, I received a mail from\u00a0some Smile’s manager, notifying me that Woozweb would be shut down on May 13th. As of writing these lines (around 4 am), the site is indeed closed.<\/p>\n
Such sites\u00a0may seem stupid, or incomplete. And sure, the service those provide is really limited.
\nYet when your monitoring setup is located in the same vLAN, or some network connected to the service you are monitoring, you should keep in mind your view on this service is not necessarily what your remote users would experience with. Hence, third-party services could stumble upon failures\u00a0your own setup won’t even suspect.<\/p>\n
Now Woozweb wasn’t perfect. Outdated web interface, outdated nagios probes (that failed establishing ssl handshake against my tlsv1.1\/tlsv1.2 only services), 10 checks limitation, never got a response from their support, … But it did the job, allowed string matches, graphed response times, used to warn me when those reached a threshold, …<\/p>\n
<\/a>Uptime Robot dashboard<\/p><\/div>\n
In the last couple days, I’ve been trying out alternatives to their service. There’s quite a lot of them, such as Pingdom. We’ll focus on free services, allowing https checks and triggering mail notifications.<\/p>\n
The first I did test and could recommend is Uptime Robot<\/a>.<\/p>\n Their interface is pretty nice\u00a0and\u00a0original. Service is free as long as you can stick to 50 checks with a 5 minutes interval, don’t need\u00a0SMS notifications and can bear with 2 months of logs retention.<\/p>\n Uptime Robot check view<\/p><\/div>\n Defining checks is relatively easy, first results show up pretty quickly, no trouble checking tlsv1.1\/tlsv1.2-only services. Already received an alert for a 1 minute outage, that my Icinga setup also warned me about.<\/p>\n Compared to Woozweb, the features are slightly better, whereas the web interface is definitely more pleasant. Yet there is no data regarding where those queries were issued from, and their paid plan page doesn’t mention geo-based checks – which is usually the kind of criteria we could look for, relying on such services.<\/p>\n StatusCake dashboard<\/p><\/div>\n Not being completely satisfied, I looked for an other candidate and ended up trying out StatusCake<\/a>.<\/p>\n Again, their site is pretty agreeable. Those used to CircleCI<\/a> would recognize the navigation bar and support button. Free plan includes an unlimited amount of checks, as long as 5 minutes granularity is enough, and does involve running checks from random locations – whereas paid plans would allow you to pick from “60+” locations (according to their pricing page, while their site also tells about servers in over 30 countries and 100 locations around the world).<\/p>\n StatusCake check view<\/p><\/div>\n Defining checks is pretty easy. I liked the idea\u00a0of being forced to define a contact group – which would allow you to change\u00a0the list of recipient alerts should be send to, for several checks at once. Yet the feature that definitely convinced me with Slack<\/a> integration. The check view confirms your service is monitored from various locations. It is maybe a little less appealing\u00a0than Uptime Robot, but the Slack integration beats everything.<\/p>\n Another big advantage StatusCake has is their “Public Reporting<\/a>” capabilities. I’m not sure I would use it right now, as I already wrote a small shell-script based website<\/a>, serving as public reporting dashboard, that I host outside of our production setup.<\/p>\n Bearing in mind these service won’t\u00a0exempt you from setting up some in-depth and exhaustive monitoring of your resources, they still are a nice addition.\u00a0Sexy\u00a0dashboards\u00a0definitely help\u00a0–\u00a0I wouldn’t have shown Woozweb screenshots, as their UI\u00a0was amazingly despicable. Today, a post on a service that closed today, and investigating on potential replacements. In the last few years, I worked for Smile, a french Open Source integrator. Among other things, Smile hosted Woozweb, a free service allowing you to define HTTP checks, firing\u00a0mail notifications. Since I left Smile, I’ve opened an account on Woozweb, […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[8,10,7,6,2],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/370"}],"collection":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=370"}],"version-history":[{"count":11,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/370\/revisions"}],"predecessor-version":[{"id":386,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/370\/revisions\/386"}],"wp:attachment":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=370"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=370"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=370"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/a><\/a><\/a>
\nSo even if you do not want to pay for a plan including SMS notifications, you could receive notifications on your\u00a0phone using Slack.
\nEverything’s not perfect though: string matches are only allowed using paid plans. This kind of feature is pretty basic, … On the bright side, status-code based filtering is nicely done.<\/p>\n
\nI’ll probably keep using both Uptime Robot and StatusCake.<\/p>\n","protected":false},"excerpt":{"rendered":"