Transactions

Doctor Droid enables you to define "Transactions"(also called as monitors in some places in the platform) which help you monitor the relative behaviour between interlinked yet independent events, the common case in stateful systems. That way, you can easily detect anomalies and breakage in customer experience on an individual or on an aggregate level.

What are transactions?

Transactions are joins you define on your events which you expect to be followed for great customer experience.

To define a transaction, you choose two events from the set of events you have been sending. We'll call them E1 & E2. You choose how to join those events together by selecting one key from each of them. We'll call them K1 & K2. If they both has some key with same name, that is pre-selected. Using this, Doctor Droid will know how to detect the second event relative to the first event.

Unique Properties of a Transaction:

Compared to individual events, here are some properties, unique to a transaction:

1. Transaction time: The time to go from primary state to secondary state in a transaction.
2. Transaction status: Active or Finished, depending on whether it has reached the terminal state or not.
3. Transaction triggers: Rule-based alert configured on the transaction time, status or any other attribute associated with the transaction

What can you do with transactions?

Once you define a transaction, here are some out-of-the-box capabilities that we provide:

1. Alert rules on transactions success rate:
   You can configure triggers on transaction success/failure rates, at both aggregate levels as well as individual transactions. Read more about triggers and their details here.
2. Track metrics related to the transaction and any of its associated attributes:

3. Filter transactions
   1. What are the currently active transactions?
   2. Search transactions by any variable, irrespective of whether they are in the primary event or secondary event

To get started with setting up a transaction, click here.