Alerting Endpoint Server
The alerting endpoint server is used to store user specifications to create notification endpoints for use with all other Alerting features.
Create, Read, Update and Delete endpoint configurations in the Opni Alerting Endpoint Server
- Persist endpoint user configurations
- Validate input information
- Alerting/Endpoints admin UI page
Accepts GRPC proto messages, converts them to OpniReceiver interfaces. OpniReceiver interfaces Must construct to valid AlertManager receivers.
Converts to underlying AlertManager receiver structs, therefore:
- to extend functionality (by writing methods on receiver structs), we must freeze the receiver code into pkg/alerting code
- !! ensure that the frozen code matches the AlertManager version used by the AlertingBackend
- any endpoint configuration must convert to an always valid receiver struct
- (K,V) stores that maintain many/all revisions (like etcd) can lead to update performance issues
- Endpoint storage interface is wrapped in an Alerting Secret store interface, which allows backend processes to request unredacted information, and any read call defaults to redacted (such as from the UI)
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.
Tied to Gateway High Availability.
WIP
- Unit tests cover redacting and unredacting secrets in protocol buffers defining
AlertEndpoints - Alerting storage client set tests the alerting endpoint storage
- Integration tests cover creating endpoints through GRPC apis
N/A
Verify we can Create, Update and Delete endpoints through the UI.