Skip to content
This repository was archived by the owner on Feb 28, 2025. It is now read-only.

Alerting Ops Server

Alexandre Lamarre edited this page Jan 23, 2023 · 8 revisions

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:

WIP

Description

WIP

Diagram

Alerting Ops Server Breakdown(1)

Responsibilities

WIP

Corresponding UI element(s)

Description

WIP

Screenshots

WIP

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:

A description of how the system will be scaled and the expected performance characteristics, including any performance metrics that will be used to measure success.

Security:

A description of the security considerations for the system

High availability:

A description of how the system will be designed for high availability, including any redundancy or failover mechanisms that will be implemented.

Testing:

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

Clone this wiki locally