title: "Terminology" date: "2024-08-07" description: "This page provides a comprehensive guide to the key terms and concepts used in Notification Center." search: exclude: true noindex: true
Terminology
This page presents the key terms and concepts used as the basis for Notification Center.
Term | Description |
---|---|
Connector type | A third-party destination or sink that the product supports, such as Slack, PagerDuty, etc. |
Connector | A configuration of templates with conditions for connecting to a third-party destination or sink of a certain type, such as “slack-workspace-1”, “slack-workspace-2”, “My_PagerDuty” or “My_HTTPS_Website”. Users can define multiple connectors for the same connector type. |
Entity type | The general data serving as the source of the notification (e.g., alerts ). |
Entity subtype | A subtype of a entity, consisting of an an alert type, an alert condition, and a triggered or resolved status. (e.g.,metricThresholdMoreThanTriggered ). |
Preset | A configuration of templates with conditions, defining the content of the message configuration. |
Template | A blueprint for some output data (e.g., Alert has been {{alert.status}} - Priority: {{alertDef.priority}} on {{alert.timestamp}} ). Templates are written in Tera programming language. |
Theme
Light