Ruuter Error Handling (REHA)

[turnerrainer]

AS AN Architect
I WANT all Ruuter technical errors to be logged centrally if it has been defines so in settings
SO THAT error logging would be identical throughout all DSLs

AS A Developer / Service Manager / Security Specialist
I WANT TO get full overview of errors on any step of Ruuter DSL from a database
SO THAT I could build services based on that database instead of processing raw log files potentially containing sensitive information

Acceptance Criteria

• Functionality can be swithced on / off from Ruuter settings file
• If switched on, All errors Ruuter within any DSL step are logged
• Errors are sent to an external endpoint, using OpenSearch by default
• Update readme.md regarding appropriate functionality with sample usage

[1AhmedYasser]

Requested Change:

1. Should report any endpoint that returns a status code <=300 and <= 500 not only exceptions

[1AhmedYasser]

Additional features requested:

1. Possibility to create a cron task inside an api

2. Possibility to pass body and params to http request, you can also add headers (Optional)

Not in this task