Alerting Monitor service exposes a REST API that serves as a backend for the Web UI, which in turn allows users with administrative privileges to configure Alerts
based on telemetry collected by the Edge Node Observability Stack. The service allows configuration of:
Alert Definitions
- a pre-defined set ofAlerts
that can be turned on/off and tweaked via settingThreshold
andDuration
Alert Receivers
- allows to selectemail
recipients from a set of allowed addresses provided by Keycloak IAM
The Alerts
generated as a result are exposed:
- via
REST API
for consumption by the Web UI - via
email
if an externalEmail Server
was provided
Read more about Alerting Monitor in the Documentation.
To set up the development environment and work on this project, follow the steps below.
All necessary tools will be installed using the install-tools
target.
Note that docker
and asdf
must be installed beforehand.
The code of this project is maintained and released in CI using the VERSION
file.
In addition, the chart is versioned with the same tag as the VERSION
file.
This is mandatory to keep all chart versions and app versions coherent.
To bump the version, increment the version in the VERSION
file and run the following command
(to set version
and appVersion
in the Chart.yaml
automatically):
make helm-build
To install all the necessary tools needed for development the project, run:
make install-tools
To build the project, use the following command:
make build
To lint the code and ensure it adheres to the coding standards, run:
make lint
To run the tests and verify the functionality of the project, use:
make test
To build the Docker images for the project, run:
make docker-build
To package the Helm chart for the project, use:
make helm-build
To push the Docker images to the registry, run:
make docker-push
To push the Helm chart to the repository, use:
make helm-push
To load the Docker images into a local Kind cluster, run:
make kind-all
To generate API code from openapi definition, run:
make codegen-all
To generate code from protobuf definitions, use:
make proto
To verify if database migration files reflect the current schema, run:
make verify-migration
To generate migrate files after database schema update, run:
make codegen-database
Details regarding email notifications via MailPit can be found here: Email Notifications.
To learn how to contribute to the project, see the Contributor's Guide.
To learn more about the project, its community, and governance, visit the Edge Orchestrator Community.
For support, start with Troubleshooting or Contact us.
Edge Orchestrator Alerting Monitor is licensed under Apache 2.0 License.
Last Updated Date: {March 27, 2025}