search

SaintAngeLs / courier_app

Courier-hub application build up with .net and React
3 stars 2 forks source link

Consul #54

Open eggwhat opened 11 months ago

eggwhat commented 11 months ago

I don't know if it is an issue on my end but after a service is registered with consul, they get critical failure check because of ping in appsetting.json. They are failing this check "pingEnabled": true "pingEndpoint": "ping", "pingInterval": 3, "removeAfterInterval": 3 So to make things work i had to disable ping for all services on my current working branch "mailing". "pingEnabled": false,. After such change everything works fine.

eggwhat commented 11 months ago

I also realized that port for consul in appsettings.json is not matching the port that service runs on. It's a case for almost all services.

SaintAngeLs commented 11 months ago

I also realized that port for consul in appsettings.json is not matching the port that service runs on. It's a case for almost all services.

You are right, I do use the other port for this micro infrastracture services, also for the dev reasons there is no need to be sure the consul is accepting all the request. We will update the settings for all the infrastructure services later.

SaintAngeLs commented 10 months ago

But it is ot fixing the issue. This solution hiddes the information.

eggwhat commented 10 months ago

Then it is worth to notice that currently on development branch Customers, Orders, Parcels services have ping set to false

SaintAngeLs commented 10 months ago

Maybe there is a point it worth, in case the consul is running as a container image and the ping is set to false, all the listed microservices are not visible.

SaintAngeLs commented 10 months ago

Still there may not be the moment to worry about, as It is only one microservice, and it will be possible to make the requests directly to host it will have. The one large issue to worry about is #112