The following tasks cover the technical side of request monitoring. They are meant to provide a near real-time overview of the actual current state of the Messaging BB to Product Owners, Service Managers, and Developers the least, but to any other interested party with appropriate permissions as well.

These tasks are not meant to cover behavioral testing but focus on detecting technical errors and other mismatches that do or may result in faulty service providing.

Implementing these tests is one of the base requirements to be able to track the ongoing quality of work of Developers, but also to provide SLA for the service to the End Clients.

These tasks are equally used for both (acceptance) testing and actual monitoring in a production environment.

Using logs as input for technical testing and monitoring purposes

It is important to have one source of truth when detecting technical errors. Using application logs for it makes it more reliable to have an actual overview of successful and unsuccessful queries, while application-based error detection relies a lot more on a specific developer and their quality of work.

Also, in the case of using many similar, but technically different applications (or when having a complete re-make of the application) to provide the same functionalities, using logs as the source for testing and monitoring makes it possible to re-use the tests and validations created so far. It is not possible when applying standard unit tests and application-specific tests.

Thereby it is highly important to make sure that the base requirements for having application logs as an actual and complete reflection of application requests and their responses are met.