Model Non-conformance Interpretation

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 vets-service and prometheus-kube 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/docker/prometheus/Dockerfile#L31	31

Sequences extracted from the static model that should produce dynamic behavior for link between vets-service and prometheus-kube

github_repository → config_server → api_gateway → vets_service → prometheus_kube
github_repository → config_server → vets_service → prometheus_kube
customers_service → discovery_server → api_gateway → vets_service → prometheus_kube
api_gateway →(implicit) user_service →(implicit) api_gateway → vets_service → prometheus_kube
api_gateway → vets_service → prometheus_kube
discovery_server → api_gateway → vets_service → prometheus_kube
user_service →(implicit) api_gateway → vets_service → prometheus_kube
config_server → vets_service → prometheus_kube
visits_service → discovery_server → api_gateway → vets_service → prometheus_kube
api_gateway → vets_service → tracing_server → discovery_server → api_gateway → prometheus_kube
config_server → vets_service → discovery_server → api_gateway → customers_service → prometheus_kube
api_gateway → customers_service → discovery_server → api_gateway → vets_service → prometheus_kube
api_gateway → vets_service → discovery_server → api_gateway → prometheus_kube
config_server → admin_server → discovery_server → api_gateway → vets_service → prometheus_kube
config_server → api_gateway → vets_service → prometheus_kube
config_server → api_gateway →(implicit) user_service →(implicit) api_gateway → vets_service → prometheus_kube
vets_service → discovery_server → api_gateway →(implicit) user_service →(implicit) api_gateway → prometheus_kube
vets_service → discovery_server → api_gateway → prometheus_kube
github_repository → config_server → vets_service → discovery_server → api_gateway → prometheus_kube
tracing_server → discovery_server → api_gateway → vets_service → prometheus_kube
admin_server → discovery_server → api_gateway → vets_service → prometheus_kube
config_server → discovery_server → api_gateway → vets_service → prometheus_kube
discovery_server → api_gateway →(implicit) user_service →(implicit) api_gateway → vets_service → prometheus_kube
discovery_server → api_gateway → vets_service → discovery_server → api_gateway → prometheus_kube
vets_service → discovery_server → api_gateway → vets_service → prometheus_kube
vets_service → discovery_server → api_gateway → visits_service → prometheus_kube
config_server → vets_service → tracing_server → discovery_server → api_gateway → prometheus_kube
user_service →(implicit) api_gateway →(implicit) user_service →(implicit) api_gateway → vets_service → prometheus_kube
visits_service → tracing_server → discovery_server → api_gateway → vets_service → prometheus_kube
vets_service → tracing_server → discovery_server → api_gateway → prometheus_kube
api_gateway → vets_service → discovery_server → api_gateway → customers_service → prometheus_kube
api_gateway → tracing_server → discovery_server → api_gateway → vets_service → prometheus_kube

Sequences that occurred in the dynamic model that should produce dynamic behavior for link between vets-service and prometheus-kube

No sequences were found in the dynamic model that actually produced dynamic behavior for the link between vets-service and prometheus-kube

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.

Non-conformance type: dynamic

Involved services