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 ofAlertsthat can be turned on/off and tweaked via settingThresholdandDurationAlert Receivers- allows to selectemailrecipients from a set of allowed addresses provided by Keycloak IAM
The Alerts generated as a result are exposed:
- via
REST APIfor consumption by the Web UI - via
emailif an externalEmail Serverwas 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-buildTo install all the necessary tools needed for development the project, run:
make install-toolsTo build the project, use the following command:
make buildTo lint the code and ensure it adheres to the coding standards, run:
make lintTo run the tests and verify the functionality of the project, use:
make testTo build the Docker images for the project, run:
make docker-buildTo package the Helm chart for the project, use:
make helm-buildTo push the Docker images to the registry, run:
make docker-pushTo push the Helm chart to the repository, use:
make helm-pushTo load the Docker images into a local Kind cluster, run:
make kind-allTo generate API code from openapi definition, run:
make codegen-allTo generate code from protobuf definitions, use:
make protoTo verify if database migration files reflect the current schema, run:
make verify-migrationTo generate migrate files after database schema update, run:
make codegen-databaseDetails 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}