Alerting

Alerting Architecture

Summary

Opni Alerting is a combination of an

• Alerting backend for dispatching alerts and messages to users
• Gateway plugin for :
  • Managing the configuration & scalability of the Alerting backend
  • Managing integrations with other Opni backends that hold observability data, called Datasources
  • Creating, reading, updating and deleting data to persist user configurations for:
    • Data used by the Alerting Plugin
    • Data needed to persist user configurations

Alerting terminology

• Conditions : Specifications around how to evaluate observations in the system , e.g. How do we make insights about the system?
• Alerts : Active state of the system, e.g. What is happening right now in our system?
• Endpoints : End-user recipients of the state of the system, e.g. Where do we send the insights?
• Routing : How to map active states of the system to their corresponding user endpoints, e.g. How do we send the right information to the right place?
• Datasource : Some external backend in the system where we can make concrete evaluations on data, e.g. What data is accessible to make insights on?)

Components

• Alerting Gateway Architecture
  • Alerting Backend
  • Alerting Endpoint Server
  • Alerting Condition Server
  • Alerting Trigger Server
  • Alerting Ops Server
  • Alerting Routing Model

Testing

Currently e2e testing of the Alerting system is done manually.