Deduplication for Ticket Alerts

The Aisera GenAI Platform includes an alert micro-service pass-through system that deduplicates and correlates alerts. This de-duplication exists in the Alert Ingestion API as well as in the Data Source Ingestion via the UI.

After the deduplication and correlation process, the service forwards this data to the integrated SOR system.

This micro-service integrates with the Aisera system Events functionality. After deduplication, the system fires an alert creation event and the event service picks it up. Then this event can be added to a workflow that creates the alert in the SOR or sends a notification.

The Alert Micro-service:

1. Uses a streaming api to read data within a sliding time window.

2. Keeps track of unique alerts and identifies duplicates in a time window.

3. Keeps all alerts in a data lake.

4. The unique alerts are forwarded to an incident service that calls new or existing models to correlate the alerts.

5. The duplicate alerts are persisted in a data store until they are no longer needed.

Duplicate Alert Data is Stored by ID