β’ πππ₯ I reverted to the old uptime monitoring solution for now. The dashboard for uptime will look as it did before all the changes. I'll do my best to integrate this better over the month of April and May. Thank you all for your patience on this β€οΈ
The official companion update & changelog blog to Tinylytics.
Vincent here. I've been monitoring the new uptime monitoring and I'm at the stage where it hasn't passed the test of "it just works". Thank you all, who have emailed, to let me know about false positives and some other quirks. Seems writing my own and "this is going to be useful" functionality is harder and quirkier than I expected (even though "it works for me"). With that in mind, this has been a failure on my part. I will be working on rectifying this over the course of a week. For now monitoring will continue and I apologise if...
β’ π Fix an issue with the uptime monitor where when the site goes down, and then comes back up, where no "Recovered" email was sent and where no event log was present for when it came back up.
And we're back. Thanks for watching π
Doing some emergency maintenance on the server. Will be back online soon.
β’ β€οΈ Upgrade emails will now be sent manually with my own human oversight instead of being automated. Sorry for letting that slip over the past weeks.
Over the past weeks I have worked hard to bring some more features to the platform, unfortunately I think that was a slight misstep on my behalf, especially around some automation and uptime monitoring. Over the next few weeks I'll be working on rectifying this. 1. I'll disable the automated checks for when the emails send out for upgrading your plan (when on the free plan). Right now it'll send an email even if you are slightly above the free usage on a 3 month basis. This has not been my intention. 2. Uptime Monitoring has seen a big upgrade,...
β’ πΎ Added better handling of recording Kudos by moving it to a background process. There are also rate limits applied to the endpoint to make sure it's not abused (growing pains, huh?). If you see anything amiss, let me know. β’ π§Ή Made further tweaks when a "please upgrade" email is sent to allow for a bit of more leeway.
β’ βοΈ Tweaked the criteria for sending "Please consider upgrading" emails so that it allows for some bursting over a 3 month period.
β’ πΎ Added the ability to manually pause and resume an uptime monitor β useful if you want to keep a history of events, or making bigger changes to your sites that might have planned outages.
β’ π Fixed an issue where uptime monitoring would send a "Critical Downtime" email, followed by an "Up" email in the same second. Please let me know if you find any other weirdness.
β’ π Fixed some issues with uptime monitoring where it would not mark a site back up and running even though it was. Also improved the logic of correctly setting states of up or down and doing the right thing (huh?).
β’ π Uptime Monitoring had a big upgrade today, with everything happening in-house right from Tinylytics. This has been a long time in the making (started last night, and finished this morning π ). All previous monitors have been migrated to using this system, so you might have had a duplicate email here and there as I was fixing a few bugs with being blocked by some Firewalls or too many attempts. I wrote about how it all works on the docs page hereΒ including some set up you might require if you sit behind Cloudflare or similar. It's a big upgrade...
Emails are sending again from our provider. All report emails should have been delivered that were pending (albeit a little later than usual). Thanks for your patience.
We're currently experiencing some downtime with our mail provider, and email reports and others are stuck in their queue. Monitoring and you might receive the emails a little than usual.