Entity types

Notification Center sends notifications based on entity types. An entity type is a Coralogix component that can generate a notification request, such as an alert or a case. Each entity type contains one or more entity subtypes, which define the structure and schema of its notifications.

Notification Center currently supports two entity types: Alerts and Cases.

Work with alert entities

Alert entities generate notifications when alert conditions are met. Each alert subtype defines the schema used to format the notification.

Supported alert subtypes

All supported alert subtypes, including EntityType and EntitySubType, are listed in the Alerts API

Access alert schema references

• :coralogix-general-code-medium: General reference
• :coralogix-actions-search-medium: Context reference: Describes the _context variable for metadata such as trigger details. See Dynamic templating

Work with Case entities

Case entities track and manage correlated events in Coralogix. When Case lifecycle events occur, Notification Center generates notification requests that can be routed to external destinations.

Supported Case subtypes

Entity	Subtype	Status	Description
Cases	CREATED	OPEN	A Case has been created and is open.
Cases	ACTIVE	OPEN	The Case is active and remains open.
Cases	ACTIVE	ACKNOWLEDGED	The Case has been acknowledged.
Cases	RESOLVED	CLOSED	The Case is resolved and closed, with optional resolution metadata.

All supported Case subtypes are listed in the Cases API.

Notification triggers

Case routing rules support specific lifecycle triggers that control when notifications are sent:

Trigger	When it fires
Activated	Impact is confirmed and the Case becomes active
Acknowledged	Someone takes ownership of the Case
Resolved	Underlying indicators are healthy and the Case is resolved
Closed	Follow-ups are complete and the Case is fully finished
Priority changed	The Case priority level is updated
Assignee changed	The Case is assigned or reassigned

Alert routing rules support two triggers: Triggered (when the alert condition is detected) and Resolved (when the condition returns to normal).

Routing and Ownership Tags

Cases use Ownership Tags--environment, service, and team--for routing. These are the same attributes used in Infra Explorer Ownership Tags, so labels already defined on your infrastructure carry through to notification routing.

Unlike alerts, which use explicit routing.<key>: <value> labels, Cases inherit their routing labels from the Ownership Tags assigned to the underlying infrastructure.

Access Case schema references

• :coralogix-general-code-medium: General reference: Alert Schema
• :coralogix-actions-search-medium: Context reference: Describes the _context variable for Case notifications. See Dynamic templating

Next steps

Explore how entities, routers, connectors, and presets work together in Core concepts in Notification Center.