Skip to content
This repository was archived by the owner on Dec 19, 2020. It is now read-only.

The issue creator receives logs with a log receiver component and creates issues from the logs.

Notifications You must be signed in to change notification settings

OMNI-SLO-Monitoring/issue-creator

Repository files navigation

Issue Creator

The Issue Creator retrieves logs from the Kafka Queue described in and instantiated with the Error-Response Monitor. Based on the services that have been registered and thus saved in a service database with the Monitoring Service Selection View in the Monitoring Frontend, the Issue Creator will either accept the retrieved log, convert it into an issue and dispatch it to Sandro's API if it pertains to a registered service or ignore the log otherwise. The log with the corresponding issue id received from Sandro's API will then be saved in a log database.

Description

Nest framework TypeScript starter repository.

Installation with docker compose

$ docker-compose build

Running the app with docker

$ docker-compose up

Start the database only:

$ docker run -d -p 27017:27017 mongo

If the database is running you can use:

$ npm run start

Usage

The issue creator sits at localhost:3500. 
If installed with docker the database is available at localhost:27017.
Post Request to localhost:3500 to add logs.
Get Request to localhost:3500/issue/:issueID with a valid issueID to get the associated issue
Get Request to localhost:3500 to get all logs.
A valid component ID has to be specified in the .env file under 'BACKEND_COMPONENT_ID' in order to receive an Issue ID

About

The issue creator receives logs with a log receiver component and creates issues from the logs.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 8