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

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

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

3. Filtering: You can filter out entities basis.

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

5. 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.

Entity Triggers

There are 3 types of triggers that are currently enabled within the scope of entities.

1. If an entity is stuck at a specific state
2. Occurrence of an event within an entity
3. Occurrence of an event, more than n times (threshold) within an entity

Watch this video to learn more about the different entity level alerts.