Bringschuld

Simple periodic task and email monitoring

Featured Embed

Periodic tasks, like cron-or email-jobs can fail silently. Bringschuld alerts you via text message and email the minute a task didn't run.

Reviews
  • Pros: 

    No frills, simply does it job

    Cons: 

    None so far

    We’ve been using Bringschuld since its very first beta version, and are very happy with it. Believe me, you want to be noticed about failing regular tasks as soon as possible ☝️ – it has already saved us a few times.

    Stefan Daschek has used this product for one year.
  • Sissi
    Sissiself-made princess
    Pros: 

    Extremely easy to use

    Cons: 

    None

    Wanna know the designer cause wow

    Sissi has used this product for one year.
Discussion
You need to become a Contributor to join the discussion.
Calvin Claus
Calvin ClausMaker@calvin_claus · Maker
Hello Product Hunt 👋 👉 Background story So @noniq is the person officially responsible for kicking my ass 👟 💕 💥 to get me to learn new things and I absolutely love him for it. Last year he got me to pick up Ruby on Rails and told me to just code “anything” to get to grips with the framework. But…I wanted to create something that would be useful to the community. After we found out that neither @noniq's consultancy nor the agency I work at, had a great solution for periodic task monitoring I knew that I had to build a tool for that 💪🏽. While building Bringschuld I was heavily interacting with them to work out what the dream periodic task monitoring tool looks like. I am really proud of the product that emerged and thrilled to share with the developer community 🤗. 👉 Product 👎 Example problem: You have a backup task that runs every 24 hours and you expect it to finish within five. If you want to be sure the backup ran you have to manually check it worked...every day. That's a real pain! 👍 Solution: Tell Bringschuld when you are expecting your backup task to run by entering its cronrule or defining a custom interval. You then modify your backup task so whenever it finishes successfully it sends a request to Bringschuld notifying that the backup has completed successfully. We call this a check-in. If, for any reason, the backup fails to complete you will receive an alert (email or sms) the minute the specified maximum run time of five hours has passed. Now you can completely forget about the task. You will only hear about it if it fails to check-in with Bringschuld. All your periodic tasks are in one dashboard 🎛, so you know that cronjob you set up 2 years ago exists and is still going strong 🔥! 🚗 Real World Example: This blog post https://medium.com/@calvinclaus/... also shows how we used Bringschuld in https://mycryptolambo.com. 👉 What sets Bringschuld apart 📩 Check-Ins can be sent via E-Mail, which means you can check if a periodic email task, like a daily newsletter, is actually sending mails. ⚡ Alerts are lightning-fast - sent a minute after the maximum run time passes, at the latest. 🚨 If your task checks in too often, or at a weird time, that's usually not what you want! Bringschuld alerts about multiple check-ins during an interval, or check-ins outside of the planned run time of your task. 💁🏼‍♀ For your convenience Bringschuld sends weekly summary mails. 👉 The name? Weeeell in German we have a one-word-name for anything. Like Wanderlust. So "Bringschuld" is German for "debt which must be delivered to the creditor". It's an analogy: your tasks have to deliver a check-in to our servers (the creditor). You can follow me on Twitter to see what I'm up to @calvin_claus