MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Automation

Alert Management

Rules that watch an instrument’s market value and fire when a condition is met — optionally sending you a notification.

Where you will find this

Alerts.

Purpose

An alert rule pairs an instrument and metric with a comparison and threshold. When it’s evaluated against the live quote and the condition holds, it raises a trigger, records it, and can notify you through your chosen channel.

The Alert Management module provides a central business capability for defining, generating, managing and tracking business alerts across the platform.

It enables timely identification of significant business conditions that require user awareness or operational attention.

The module serves as the platform-wide business alerting capability.

Objectives

The module will:

  • Define business alert rules.
  • Generate alerts from business events and scheduled activities.
  • Classify alerts.
  • Prioritise alerts.
  • Support alert acknowledgement and resolution.
  • Maintain alert history.
  • Enable proactive operational monitoring.

Functional Scope

The module includes:

  1. Alert Definition
  2. Alert Rule Management
  3. Alert Generation
  4. Alert Classification
  5. Alert Prioritisation
  6. Alert Lifecycle Management
  7. Alert History
  8. Alert Search
  9. Alert Audit

Alert Model

An alert represents a business condition that requires attention.

Alerts may originate from:

  • Business Events
  • Scheduled Activities
  • Business Rules
  • System Monitoring
  • External Integrations

An alert remains independent of its notification method.

Alert Definition

The platform will support definition of business alert rules.

Typical alert categories include:

  • Market Alerts
  • Strategy Alerts
  • Order Alerts
  • Position Alerts
  • Portfolio Alerts
  • Risk Alerts
  • System Alerts
  • User Alerts
  • Integration Alerts

The design will support additional alert categories.

Alert Rule Management

Each alert is governed by one or more business rules.

Typical rule characteristics include:

  1. Trigger Condition
  2. Business Context
  3. Priority
  4. Severity
  5. Validity Period
  6. Escalation Policy

Alert rules remains configurable.

Alert Generation

The platform will generate alerts when defined business conditions are satisfied.

Typical alert sources include:

  1. Event Management
  2. Scheduler
  3. Strategy Deployment & Execution Engine
  4. Risk Management
  5. Portfolio Management
  6. Live Market Data
  7. Webhook & External Signal Management

Alert generation is automatic.

Alert Classification

Alerts is classified according to business significance.

Typical classifications include:

  • Informational
  • Advisory
  • Warning
  • Critical

The classification model remains extensible.

Alert Prioritisation

The platform will assign priorities to alerts.

Typical priorities include:

  • Low
  • Medium
  • High
  • Urgent

Priority will support operational decision-making.

Alert Lifecycle Management

Each alert will progress through a defined lifecycle.

Typical lifecycle states include:

  1. Created
  2. Active
  3. Acknowledged
  4. Escalated
  5. Resolved
  6. Expired
  7. Closed

Lifecycle history is preserved.

Alert History

Historical alerts is retained.

History includes:

  • Alert Category
  • Alert Source
  • Alert Priority
  • Alert Status
  • Creation Timestamp
  • Resolution Timestamp

Historical records remains immutable.

Authorised users is able to search alerts.

Typical search criteria include:

  • Alert Category
  • Priority
  • Status
  • Source Module
  • Instrument
  • Strategy
  • Portfolio
  • User
  • Date Range

Search capabilities will support operational management.

Business Rules

  • Every alert will have a unique identifier.
  • Every alert will belong to one alert category.
  • Every alert will have one originating source.
  • Every alert will have one lifecycle state.
  • Alert acknowledgement does not remove the alert.
  • Resolved alerts remains historically available.
  • Alert generation does not modify business data.
  • Historical alert records will never be deleted.

Audit Requirements

The platform will maintain an audit trail for alert activities.

Audit events includes:

  • Alert Creation
  • Alert Classification
  • Alert Acknowledgement
  • Alert Escalation
  • Alert Resolution
  • Alert Closure
  • Alert Archive

Audit records remains immutable.

Out of Scope

The following are outside the scope of this module:

  • Notification Delivery
  • Email Transmission
  • SMS Transmission
  • Push Notification Delivery
  • Webhook Processing
  • Strategy Execution

These responsibilities belong to their respective business modules.

Create an alert

  1. Choose the instrument and the metric to watch (e.g. last price).
  2. Set the operator and threshold — e.g. price greater than 2500.
  3. Optionally pick a notification channel.
  4. Activate it. When evaluated and met, it fires a trigger and notifies you.