Non-conformance type: dynamic

This is a non-conformance of which there was code evidence collected for this link, but no calls were detected between the two services at runtime.

Involved services

Potential interpretations for the non-conformance

Unused / Unreachable Code

The line of code that is responsible for triggering a flow of communication between the two component is not reachable or the line is not used at all in the implementation. It could be the case that the function that should call this line is not implemented, commented out or wrapped in a code-block (e.g. if-else statement or switch statement) that is never executed.

Misconfiguration of Service

One of the most common causes for failures in microservice systems is misconfiguration of services; usually different third-party services (or libraries) are used in project and each needs to be configured independently. If a service is not configured properly, it might not be reachable for other services that are trying to communicate with it.

Service Registration Issue

The service might not have been (correctly) registered at the service registry component. If it isn't registered at the service registry component, then other services do not which address and port they should use to initiate communication with this service.

The folowing information could help with understanding of the detected non-conformance:

The following line of code should produce a call between config-server and department-service but no such call was seen during dynamic.

No data dynamic data was found for config-server and department-service. Is one of involved services perhaps an external service?

The following models can be used to inspect the (sequential) behavior of each service individually:

No dynamic model was found for either of the services.