An Event Domain is like an event resolution blueprint; all events that come into xMatters have a few pieces of information that are always required (i.e., predicates). Each source of Events, such as a management system, requires a separate Event Domain.
When you add a new Company to a multiple-Company deployment, xMatters automatically creates the following default out-of-box Event Domains (and their associated script packages) for the new Company:
| Event Domain | Description and Purpose |
|---|---|
| advanced_messaging | This Event Domain is used to handle all notifications required by Scenarios in the Advanced Messaging component. For more information about this feature, refer to the xMatters User Guide. |
| default | This Event Domain handles all events that are injected without a domain, or with a domain that xMatters does not recognize. |
| devicevalidation | This Event Domain handles all messages and responses that involve validating User's Devices. |
| error_responses | This Event Domain is responsible for generating and handling responses when notifications encounter an error; for example, when a User attempts to respond to a notification for which the event has already been terminated. |
| messaging | This Event Domain handles all notifications and responses for the Quick Message panel. |
| ping | This Event Domain is used to demonstrate two-way communication between xMatters and the |
| voicerecordings | This Event Domain handles all calls and scripts required to manage the voice recordings. |
The Event Domains table identifies all of the Event Domains in the system, and provides a description for each one. The table also displays the version of the integration, and the name and revision number of the script package associated with the Event Domain.
| Note: | The number in the Version column refers to the version number of the integration associated with that Event Domain; this number is usually assigned by the xMatters integration developer, and will not generally apply to the default Event Domains. |