NOTE: This is a beta feature, undergoing fast iterations and documents might be outdated. You might have a better visibility from changelogs. Or directly message our team if you have any further queries.

What is an Entity?

An entity is a chain of events connected together using a common primary key across the data.

These entities transition into different states during these processes. They could be customers, e-commerce orders or payment refunds.

Why Entities?

Entities help stitch together all critical events associated with a specific business object, in the above mentioned case, a payment transaction.

The presence / absence of these events help identify failure points in the transaction.
The attribute values within each event helps drill-down and identify variable values within the transactions.

Entities vs Transactions vs Events

Features and capabilities of Entities

Grouping in List View: You can group together all events associated with a single instance of an entity.

Alerting: Identifying anomalies in transactions at an aggregate or individual level basis entity events.

Filtering: You can filter out entities basis.

Funnel view[BETA]: Track the state of different instances started within a certain duration

Mapping external metrics to nodes: Every node in an entity can be considered to be equivalent

To get started with creating your own entities, click here.

Below are some additional examples of state machines.

A Merchant Payment State Machine (identified with transaction ID). Every box with a border signifies a related state machine.
A Food Delivery State Machine (identified with Order ID)
A data processing state machine comprising of multiple long-running asynchronous tasks
A FinTech Trade execution state machine (identified with transaction ID)
An onboarding state machine for lending (Identified with Application ID)
An order placement state machine (identified with session_id, connected with order_id for the last step)

To get started with creating your own entities, click here.