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 admin-server and discovery-server but no such call was seen during dynamic.

Type of evidence File for evidence Line number of evidence
Link https://github.com/spring-petclinic/spring-petclinic-microservices/blob/master/admin-server.yml#L12 12

Sequences extracted from the static model that should produce dynamic behavior for link between admin-server and discovery-server

  • github_repository → config_server → admin_server → discovery_server
  • config_server → admin_server → discovery_server
  • admin_server → discovery_server → api_gateway → visits_service → discovery_server
  • config_server → admin_server → discovery_server → api_gateway → visits_service → discovery_server
  • admin_server → discovery_server → api_gateway → vets_service → discovery_server
  • config_server → admin_server → discovery_server → api_gateway → tracing_server → discovery_server
  • admin_server → discovery_server → api_gateway → customers_service → discovery_server
  • config_server → admin_server → discovery_server → api_gateway → customers_service → discovery_server

Sequences that occurred in the dynamic model that should produce dynamic behavior for link between admin-server and discovery-server

No sequences were found in the dynamic model that actually produced dynamic behavior for the link between admin-server and discovery-server

For the occurred sequences, these are the unique sequence of endpoints (parameters) that were used in the sequence

No sequences were found in the dynamic model and thus no unique sequences of endpoints could be extracted.

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

Dynamic model learned for service admin-server:

DFA 0 State 0 1 State 1 0->1 in__8080.0__>__200.0__get__user__admin-server 12 I I I->0 10 State 10 1->10 in__8080.0__>applications__200.0__get__user__admin-server 9 23 State 23 10->23 in__8080.0__>assets>js>chunk-common.530a46a5.js__304.0__get__user__admin-server 8

Dynamic model learned for service discovery-server:

DFA 0 State 0 I I I->0