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.
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.
- 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.
There are 3 types of triggers that are currently enabled within the scope of entities.
- If an entity is stuck at a specific state
- Occurrence of an event within an entity
- Occurrence of an event, more than n times (threshold) within an entity
Watch this video to learn more about the different entity level alerts.
Updated about 1 month ago