Alerting Ops Server

Alerting Ops Server

Summary:

The alerting ops server is used to:

• propagate user configurations of the Alerting backend to the Alerting backend
• periodically sync user configurations to concrete routing models

Table of contents

• Architecture
• Component n
• Scale and performance
• Security
• High availability
• Testing

Architecture:

Description

WIP

Responsibilities

WIP

Corresponding UI element(s)

• Alerting Tab / Main Page

Description

Allows the User to configure & scale their Alerting Backend.

Screenshots

Input and output interfaces

WIP

Restrictions & Limitations

WIP

Performance Issues

WIP

Testplan

WIP

Unit tests

WIP

Integration tests

WIP

e2e tests

WIP

Manual testing

WIP

Scale and performance:

In order to ensure the routing persistent data updates perform at scale, we:

• periodically run a user config sync, which checks if the user configurations have changed in a manner that updates the loaded routing model
• if they have changed in such a manner, batch the changes into a request broadcast to all connected clients.

High availability:

Tied to Opni Gateway High Availability.

Testing:

A description of the test plan, including any manual testing and steps to reproduce