spring-cloud / spring-cloud/spring-cloud-commons

Does the health check function of Spring Cloud LoadBalancer support 4-layer connectivity checks?

Open
#1,599 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

waiting-for-triage
Dominant language
Java
Stars
751
Forks
744
Avg merge
1d 14h
Merged PRs (30d)
9

Description

Is your feature request related to a problem? Please describe.
In my request, I would like to check the connectivity of the 4th layer of the service, without considering the connectivity of the 7th layer. I would like to know if it is currently supported? I examined the source code and found that currently only 7-layer connectivity is available. I understand that for a microservice framework, 7-layer checks are normal. However, my current requirement is actually to only check 4 layers because I don't know if the upper services have check interfaces, and even the upstream might not be a microservice application. Therefore, I want to perform 4-layer checks. How should I modify it?

Describe the solution you'd like
I want to know how I should modify the source code to rewrite the health check without any risks.

Describe alternatives you've considered
Can TCP layer 4 inspection be supported?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the existing Spring Cloud LoadBalancer health-check entry point and tracing the current 7-layer connectivity check. Done means the TCP layer-4 support question has a documented, tested approach that explains expected behavior and risks.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring, spring-boot
Domain
backend, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.