Tinylytics Updates

changelog

  • πŸ‘Ύ Uptime monitors that report a site down for more than 7 days will now automatically pause β€” you'll also get an email saying that this is the case. You can resume monitoring at any time.
  • πŸ§ΉπŸ‘Ύ When pausing an uptime monitor, it will now also change the "Up" or "Down" mini status to "Paused" with a yellow background.
  • πŸ‘Ύ Updated uptime monitoring to now again change check intervals depending on the site status, add info on what check period it's currently on. Also you can now pause and resume a check once again. Also changed the behaviour of check intervals when a site goes down β€” it'll check every 5 minutes instead of every minute to avoid false positives (this is a good compromise).
  • πŸ§ΉπŸ“– Updated the documentation about uptime monitoring giving more details and also IP addresses that should be whitelisted if you're using a firewall in front of your site (and the monitor is being blocked).
  • More to come and do :)
  • πŸ‘Ύ Some uptime changes are now back and you can enjoy the current status, uptime % and ssl status once again as they were with more useful info. I'll be adding more functionality and details soon.
  • πŸ›πŸ˜•πŸ”₯ 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 ❀️
  • πŸ› 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.
  • ❀️ 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.
  • πŸ‘Ύ 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 that is way more flexible, allows for features I have scribbled down, down the line and others. I did make some UI changes also, and it looks great β€” although room for improvement as I go. Enjoy.
  • 🧹🎰 Lifetime hits now have been re-synced across all sites and will reflect all correct values β€” some might see little to no change and others might see a bigger change where hits were previously deleted due to ignore paths or otherwise (when you contacted me about false positives). Lifetime hits will now re-sync automatically every few hours.
  • πŸ‘Ύ Lifetime hits now also includes a lifetime unique hit count and is show on the sites overview and dashboard.
  • 🧹 Some UI cleanup.
  • ... maybe something else that I forgot about.
  • πŸ‘ΎπŸš€ Today I improved the way hits are processed to allow much greater flow through the system. The old flow worked fine but it’s now super charged. Saying that, lifetime hits might be calculated slightly after we’ve processed a hit. This is by design. I’m monitoring this and will add an extra lifetime weekly update to make sure it’s always correct and up to date (due to the old hit collector sometimes failing to update the lifetime count). Anyway, all is looking great!
  • πŸ›πŸ‘Ύ Fixed an issue with consistently calculating average usage data for your account. This now also happens in the background once a day.
  • πŸ› οΈ Made underlying config changes to allow for greater throughput of background jobs and other server side tweaks.
  • πŸ’ŒπŸ˜… Added extra checks for email reports that marks if an email is processing before trying to send another. I hope this will "finally" fix the issues we've seen on Monday β€” again really sorry about this. Failed email reports will now try again also, for reports that sometimes get stuck (although I don't think that'll happen again).

Mid February 2025 Updates

This is a more unusual change log entry because there have been a lot of changes, and not enough blogging about it, so I thought I'll do a longer form update like this.

  • ✨ I've been working on a UI refresh across Tinylytics, which includes a new homepage, new site list and also a tweaked header area for the site overview. This is an ongoing redesign to make things a little bit more modern, without loosing what Tinylytics is. Saying that, there will be more tweak here and if you ever notice anything that doesn't look right, just let me know. Here is a before and after of the site overview page (with the header changes):
  • πŸš€ You can now set a default date filter range for your sites which will automatically be reflected when you open up the stats page or when viewing the site list. Go to your site settings page and select a filter range that suits your needs β€” we've kept the default 30 days. Note that is for paid accounts only.
    Default date filter option on the settings screen for your site.