The application provides a combined frontend for both monitors CPU-tracking-monitoring-service and the Error-response-monitoring-service, as well as the Issue-Creator.
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
The CPU-Tracking Monitor provides the possibility to add services which are to be monitored. These services as of now only comprise the Database Service. The services that are added must import the cpu-utilization-observer package which exposes an endpoint that the backend of the CPU-Tracking Monitor scrapes for the PCU load.
The Error-Response Monitor lets one define certain request parameters in its UI for testing specific endpoints in an environment that closely resembles its use cases. The user can adjust the type of request (GET or POST) and the expected response which in the case of a GET request is the response data and in the case of a POST request is the HTTP status code. In its UI, one can also fetch all logs received by the backend of the Error-Response Monitor and observe specifically the logs created by work checking the entered service endpoint.
The combined frontend also offers the feature to register multiple services that are to be monitored. Upon registration, the Issue Creator will only assess those logs retrieved from the Kafka Queue whose corresponding service is already registered. Registered services are stored in their own database which can be found in the Issue Creator repository.
All logs that are stored in the Log Message database (which is also sitting inside the Issue Creator repository) are visible in this tab.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via Protractor.