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.
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.
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.
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.
| Type of evidence | File for evidence | Line number of evidence |
|---|---|---|
| Link | https://github.com/spring-petclinic/spring-petclinic-microservices/blob/master/vets-service.yml#L22 | 22 |
No data dynamic data was found for tracing-server. Is this perhaps an external service?