Configure event domains
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.
xMatters automatically creates the following default out-of-box event domains (and their associated script packages) for each new company:
|Name||Description and Purpose|
|application||Internally used domain for communication plans (do not modify this domain; any changes will be lost during updates to the domain).|
|advanced_messaging||This event domain is used to handle all notifications required by scenarios in the Advanced Messaging component.|
|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.|
|generic||This event domain is provided as a generic integration domain to assist in creating integrations.|
|generic_responses||This event domain is responsible for handling any incoming responses that do not explicitly target any other event domain.|
|messaging||This event domain handles all notifications and responses for the Quick Message panel.|
|onboarding_notification||This event domain is used to handle messaging related to the User Upload feature.|
|ping||This event domain is used to demonstrate two-way communication between xMatters and the Integration Agent; used for testing only.|
|sms_confirmation||This event domain is used to send confirmation, help, and welcome messages to SMS devices in compliance with MMA regulations.|
|sms_deactivation||This event domain is used to send messages to SMS device owners and supervisors when a device is deactivated or delisted by a service provider.|
|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. The Export Integration button (in the Action column) allows you to export the scripts and any constants for an event domain to an XML file. For more information about this feature, see Export and import event domain information.
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.
To view and manage event domains:
- In the Manage Subscriptions menu, click Event Domains.
- xMatters displays the Event Domains page.
- Do one of the following:
- To modify an existing event domain, click its name in the list to view its details. For more information, see Define event domain details.
- To delete an event domain, select the check box for the Domains you want to delete, and then click Remove Selected.
- To export event domain information, click the Export Integration button for the event domain you want to export. For more information, see Export and import event domain information.
- To create a new event domain, click the Add New link, and then specify its details on the Event Domain Details page, as explained in Define event domain details.