Monitor cron job even more easily with our first native integration on Healthchecks.io
On request, we have now built and released Bugsnag integration, a pretty advanced error and stability management platform
📇 Download our vCard
Never miss an alert from us - download our vCard and add us in your favourites on your phone. You can also create a contact on GMail, Zoho or any other email client so our alerts don’t end up buried in updates or even spam.
Incident details page timestamps for status change now reflect the right times
User password change redirects instead of staying on the same page and displaying incorrect error message
Redirect to after login has now been fixed
The acknowledge and resolve status buttons now.. well.. err.. looks more like a button rather than a disabled tag
SMS option is now compatible for older escalation policies
⚒ Tools we discovered recently
Netdata (github) - is distributed, real-time performance and health monitoring for systems and applications. It is a highly-optimized monitoring agent. Super popular and reliable.
Monitror (website, demo) seems super promising considering the customisations and the fact that they want to be a wallboard. I know right, mind=blown
In this post, I summarize some accomplished engineer’s views on error handling. There is a distinction between errors that are caused by programmer neglecting bugs and those that represent true error conditions. The granularity of error checking is also up for debate: Per function? Per module? Jump to dialog handler in the main message loop? Kill the process and restart?