Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Consider logging new HTTP connections with DEBUG or lower level #11196
We're using a custom Hazelcast Discovery Strategy for Hashicorp Consul. We register a health-check with Consul to monitor available nodes - this healthcheck hits the Hazelcast REST endpoint repeatedly.
This results in a lot of
entries in our log.
Is there a specific reason to log new connections at
That is the work-around we're applying now. However, we've got ~50 microservices with individual logback configurations and would obviously like to avoid patching them all.
Not a big deal, but if there is no explicit reason for logging with INFO it'd make sense to change it in Hazelcast.
The reason for a rather verbose logging here is in a regular member-to-member communication connections are created/closed rarely.
Logging this at the INFO level massively helps during troubleshooting. Could you configure Consul to open a single connection and re-using it for health checks whenever possible?
I am moving this ticket to 3.9.1 as this is not a release blocker.