Table of Contents

SES Event Manager

About

The SES Event Manager is a DataMiner connector that automates event and ticket management for SES satellite operations. It polls active alarms from DataMiner elements, processes them as events, and manages the full ticket lifecycle through the DataMiner Ticketing module.

System Info

Range Linked Components Exported Components
1.0.0.x DataMiner Ticketing module -
1.1.0.x DataMiner SDM Ticketing module -

Configuration

Connections

Virtual Connection - Main

This connector uses a virtual connection and does not require any input during element creation.

Initialization

When the element has been created, the following configuration steps are required:

  1. Navigate to the Ticket Automation page and configure at least one automation rule by specifying an automation name and the corresponding DataMiner automation script name.

  2. On the CMDB Systems page, add the relevant CMDB system mappings for your environment.

    Only alarms from elements that have a matching CMDB system property configured will be processed by the connector.

  3. On the Support NOC page, add your support NOC entries and set a default NOC for ticket assignment.

  4. On the General page, set Poll Active Alarms to Enabled to start monitoring alarms.

On first startup (1.1.0.x only), the connector will automatically initialize the following:

  • A TicketType named "SES" with all required FieldDefinition objects for ticket schema definition.
  • An ExternalOwner named "ServiceNow" with the appropriate VisualizationEndpoint and ApiEndpoint.

General Configurations

The following parameters can be configured on the General Configurations page:

  • Event Evaluation Frequency (1–1800 seconds, default: 30s): Determines how often events are evaluated for ticket creation.
  • Ticket Escalation Time (10–600 seconds, default: 30s): The time before an event is escalated to a ticket.
  • Ticket Lookup Frequency: Determines how often the connector checks for ticket status updates.
  • Ticket Follow-up Delay: The delay for handling events that clear before a ticket is created.
  • Cleanup Method: Determines whether resolved events are cleaned up based on Max Number or Max Duration.
  • Event-Based Alarm Ingestion (Enabled/Disabled, default: Enabled): Enables or disables event-based alarm ingestion. When enabled, the connector automatically creates and manages a correlation rule that triggers the Alarm Forwarder automation script on qualifying alarm changes across all DMAs. The correlation rule is managed by the DMA hosting this connector. The script executes in parallel for different alarms.
  • Alarm Forwarder Correlation Rule (string, default: "Alarm Forwarder"): The name of the correlation rule created and managed by the connector. Changing this value disables the current rule and creates a new one with the updated name.
  • Alarm Forwarder Automation Script (string, default: "Alarm Forwarder"): The name of the automation script executed by the correlation rule. Changing this value updates the script reference in the active rule.
  • Show Event Ingestion Debug Page (Enabled/Disabled, default: Disabled): Controls visibility of the Event Ingestion Debug page, which displays the Alarm Forwarder buffer table. Intended for troubleshooting.

How to Use

General Page

The General page provides an overview of all managed events. Context menu actions are available on the events table for manual event operations.

Ticket Automation Page

The Ticket Automation page allows you to define rules that map automation names to DataMiner automation scripts. When a new event is detected, the connector can execute the configured script to handle ticket creation and processing according to your custom logic.

CMDB Systems Page

The CMDB Systems page is used to configure mappings between events and your Configuration Management Database. This enriches events with contextual information such as associated carriers, satellites, and services.

Support NOC Page

The Support NOC page manages your Support Network Operations Center entries. You can add multiple NOC teams and designate one as the default, which will be used for automatic ticket assignment.

Logs Page

The Logs page displays error logs generated by the connector. Automatic cleanup is applied based on the configured retention policy.

Event Ingestion Debug Page

The Event Ingestion Debug page is hidden by default and can be shown via the Show Event Ingestion Debug Page toggle button on the General Configurations page. It displays the Event Ingestion Buffer Table, which is the intermediate table where the Alarm Forwarder script pushes serialized alarm payloads. Each row is keyed by DMA ID/Root Alarm ID and includes the JSON payload and a timestamp. Rows are automatically deleted after processing; if an alarm is re-triggered while still being processed, the row is preserved for the next cycle.

Polling and Timers

The connector uses three internal timers:

  • Timer 1 (10s): Evaluates events and performs ticket lookups.
  • Timer 2 (1 min): Polls active alarms and processes ticket follow-up.
  • Timer 3 (1 hour): Runs resolved event cleanup and error log cleanup.

This is a virtual connector. No data traffic will be seen in the Stream Viewer.

Note

Event-based ingestion does not use timers. When the Alarm Forwarder script pushes a row to the buffer table, processing is triggered immediately per row via a QAction trigger on the buffer table. This provides near-real-time event creation independent of polling intervals.

Notes

SDM Ticketing Dependency

The 1.1.0.x range requires the DataMiner SDM Ticketing solution to function. The connector uses the TicketingApiHelper class to retrieve, create, and update tickets through the SDM Ticketing API.

Ticket Schema

In the 1.1.0.x range, the connector defines an "SES" TicketType on startup with all required FieldDefinition objects. Custom ticket fields are managed through TicketField instances. Fields are accessed and updated using the SetTicketFieldValue helper pattern.

Migration to New Ticketing Module

Version 1.1.0.x introduces a migration from the legacy ticketing system to the DataMiner Ticketing module built on DOM (DataMiner Object Models). If upgrading from the 1.0.0.x range, ensure your DataMiner System supports the DOM-based ticketing module before deploying this version.

Event-Based Alarm Ingestion

The 1.1.0.x range introduces an optional event-based ingestion path alongside the existing polling mechanism. When enabled:

  • The connector creates and manages a correlation rule (stored in the "SES Event Management" folder) that monitors all DMAs for alarm changes matching values in the CMDB Systems table. The rule filter checks the CMDB System property at the Alarm, Element, and Service level.
  • The correlation rule triggers the Alarm Forwarder automation script, which collects alarm details, properties, parent services, and highest table severity, serializes them, and pushes them to the connector's Event Ingestion Buffer Table (PID 7000).
  • The connector processes each buffer row immediately, creating or updating events and applying ticket rules if configured.
  • Buffer rows use DMA ID/Root Alarm ID as the key. Rapid re-triggers for the same alarm overwrite with the latest data, and a timestamp comparison ensures rows updated during processing are not prematurely deleted.

Both ingestion modes (polling and event-based) can operate simultaneously.

Minimum DataMiner Version

This connector requires DataMiner 10.5.0 or higher because of dependencies on:

  • SDM Ticketing APIs (TicketingApiHelper).
  • The DataMiner SDM Ticketing solution, which must be available on the DataMiner System.
Improve this page