You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consul reports health check problems when an application is configured for Consul to check application health instead of the application sending heartbeat
#258
Open
3 of 4 tasks
el-duderino5 opened this issue
Jun 10, 2021
· 0 comments
Example that reproduces the problem uploaded to Github
Full description of the issue provided (see below)
Steps to Reproduce
Use https://micronaut.io/launch to make a new Micronaut project, and select config-consul and discovery-consul features
Install consul through docker and add the following configuration to bootstrap.yml and application.yml. The configuration in application.yml tells the application that Consul is the one who checks for the health of the application instead of the application sending the heartbeat to Consul:
I would also like to report that there are currently inconsistencies in what is stated in the guide with respect to Consul configuration and what https://micronaut.io/launch configures for service discovery with Consul. On the official Micronaut Discovery Client guide page, it is stated that implementation("io.micronaut:micronaut-discovery-client") is needed to add the discovery client to the application but, checking what is generated with the launcher, the dependency is instead the following: implementation("io.micronaut.discovery:micronaut-discovery-client").
I have attached a picture that describes the problem.
The text was updated successfully, but these errors were encountered:
Task List
Steps to Reproduce
bootstrap.yml
application.yml
Expected Behaviour
On Consul's web client you should see that the application is running with no problems.
Actual Behaviour
Under health checks tab for the service, Consul's web client reports the following:
Get "http://localhost:8080/health": dial tcp 127.0.0.1:8080: connect: connection refused
Environment Information
Example Application
I would also like to report that there are currently inconsistencies in what is stated in the guide with respect to Consul configuration and what https://micronaut.io/launch configures for service discovery with Consul. On the official Micronaut Discovery Client guide page, it is stated that
implementation("io.micronaut:micronaut-discovery-client")
is needed to add the discovery client to the application but, checking what is generated with the launcher, the dependency is instead the following:implementation("io.micronaut.discovery:micronaut-discovery-client")
.I have attached a picture that describes the problem.
The text was updated successfully, but these errors were encountered: