Introducing Triggers by Doctor Droid

This week, we are adding Triggers functionality into our product — a feature that enables proactive tracking of transactions.

In our earlier version, we mandated users to setup alerting rules while creating a monitor. We received feedback that it commonly happens that you want to track the success rate of a transaction by setting up monitors but you don't want to setup alerts / triggers yet.

Hence, triggers.

Here's an example of a simple trigger that we have setup.

Explainer: If in the past 15 minutes (from current time), more than 3% of high value transactions have failed because of a delayed payment webhook response, it is marked as a rule violation and alert is triggered.

Curious to read more? Check out our updated triggers documentation.