Service Flow test results based on Ruuter logs

[turnerrainer]

AS A Service Manager I WANT TO have a high-level overview of the problems that are causing faults in running a Service SO THAT I could fix them in test and at least be aware of them in production

Acceptance Criteria

Below, when Faults is used, actually both Services and Elements are meant

Keeping track of Faults

• [ ] Store states of Faults in a relational database
• [ ] If there is a 1-minute (or whatever) timeframe when a Fault was working correctly and the same problem occurs again, this results in new entries in a relational database stating that 1) the previous fault was solved; 2) a new issue has been opened by making an appropriate entry to the database table and the Fault occurs again
• [ ] The decision about a Fault existing or not existing is based on Ruuter logs

Opensearch

• [ ] Index schema
• [ ] REST endpoints to populate index schema with mock data for initial testing
• [ ] Fetch data based on a specific Ruuter request ID
• [ ] Fetch data based on business-level AC requirements
• [ ] Actual Ruuter logs (see https://github.com/buerokratt/Ruuter/pull/45 as an example) are used as input for indices and mock data

ETL pipelines

ETL pipelines are out of the scope of this issue and will be done internally by Bürokratt

• [ ] Ruuter logs are transported to an appropriate OpenSearch index

Detecting Faults based on Ruuter logs

• [ ] ERROR as a response
• [ ] HTTP response codes outside of pre-defined allowed response codes
• [ ] Faults are queried from OpenSearch

[SigritSiht]

https://github.com/buerokratt/NoOps/issues/47